Try another approach to mark hanging generated tests #371 #554
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Description
Note, this issue affects JUnit 5 only!
New methods and entities were added to codegen to provide required assertion wrapper. Now tests with timeout are being abrupt just after exceeding time limit.
Fixes #371
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Manual Scenario
Set handing test timeout to 100ms and generate tests for the example:
Generated test methods should be not only annotated with
@Timeouttag but also have wrappers likeassertTimeoutPreemptively(Duration.ofMillis(100L), () -> PomXmlFinder.main(stringArray));insideChecklist (remove irrelevant options):