https://github.com/apache/servicecomb-java-chassis, b79423c19f0bcf4e622674b5b74d9162a8af7a02, org.apache.servicecomb.swagger.generator.core.processor.annotation.SwaggerDefinitionProcessorTest.should_process_security_oauth2

[Fring02]

Here's the flaky test detection in the repository https://github.com/apache/servicecomb-java-chassis on the SHA b79423c19f0bcf4e622674b5b74d9162a8af7a02. We've chosen that commit, because that commit is the first commit where the test method was introduced and got fail for flaky test. The previous commits before that simply didn't have that test method. Once it was introduced, Nondex detected flakiness.

For the ease of upload, the file has been changed to .txt format config.txt Configuration file, generated by Nondex failures.txt Listed names of tests which failed during the execution of Nondex invocations.txt Information about the number of Nondex executions on test and a number of shuffles on test orders to detect flakiness [org.apache.servicecomb.swagger.generator.core.processor.annotation.SwaggerDefinitionProcessorTest.txt] (https://github.com/TestingResearchIllinois/idoft/files/10926717/org.apache.servicecomb.swagger.generator.core.processor.annotation.SwaggerDefinitionProcessorTest.txt) Full output from console log for the test which failed during the execution of Nondex.

Here's the usual execution of test, without Nondex. It succeeds, as it can be seen.

We were working in a team of 3. Our members: Sultanbek Khassenov (skhassen@gmu.edu) - @Fring02 Athena Parker (eparke2@gmu.edu) - @NegaNote Mani Shah (mshah22@gmu.edu) - @mani9723

[winglam]

Can you add some description for what each file you uploaded contains?

[Fring02]

Can you add some description for what each file you uploaded contains?

Done, thanks.