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.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual Scenario

Set handing test timeout to 100ms and generate tests for the example:

package issue371;

import java.io.File;

public class PomXmlFinder {
    public static void main(String[] args) {
        scan(new File("C:\\"));
    }

    private static int counter = 0;

    private static void scan(File file) {
        if (counter > 10) return;
        if (file.isFile() && file.getName().equals("pom.xml")) {
            counter++;
            if (counter > 10) return;
            System.out.println(file.getAbsolutePath());
        }
        File[] files = file.listFiles();
        if (files != null) {
            for (File child : files) {
                scan(child);
            }
        }
    }
}

Generated test methods should be not only annotated with @Timeout tag but also have wrappers like assertTimeoutPreemptively(Duration.ofMillis(100L), () -> PomXmlFinder.main(stringArray)); inside

Checklist (remove irrelevant options):

• The change followed the style guidelines of the UTBot project
• Self-review of the code is passed
• No new warnings