52
Enable the test framework to have a property per test "maximum allowed time to run". Default to unlimited if not set.
The test framework should abort a test with a distinct failure when the time is exceeded.
Reason;
Switching to 2019 Wave 2 we have experienced some hard to find issues that ultiomately resulted in two infinite loops in our solution. The root cause is most likely a git merge issue where we lost a line of code. No big deal in itself, but this raises an interesting challenge for CI/CD... all we saw in test runs inside and outside of build pipelines was an out-of-memory exception which is extremely hard to debug or pin down otherwise.
Also, if we had that property we could use it to catch unexpected changes in overall performance of a tested functionality quite efficiently, too.
The test framework should abort a test with a distinct failure when the time is exceeded.
Reason;
Switching to 2019 Wave 2 we have experienced some hard to find issues that ultiomately resulted in two infinite loops in our solution. The root cause is most likely a git merge issue where we lost a line of code. No big deal in itself, but this raises an interesting challenge for CI/CD... all we saw in test runs inside and outside of build pipelines was an out-of-memory exception which is extremely hard to debug or pin down otherwise.
Also, if we had that property we could use it to catch unexpected changes in overall performance of a tested functionality quite efficiently, too.
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we might consider it in the future.
Best regards,
Business Central Team