Automating Test Case Identification in Java Open Source Projects on GitHub

This project is part of the scientific paper Automating Test Case Identification in Java Open Source Projects on GitHub.

Automated analysis

For automated analysis can be used AnalyzeProjectCommand.php that can be imported as Laravel command and executed via php artisan projects:analyse.

Results

Correlation of the word "test" and number of test cases

The full correlation analysis results are presented in the following figure.

Revealed testing practices

1. Master test - Example of Master test type in the westnordost/StreetComplete repository (JUnit4).
2. Reverse proxy test:
   • By method name - Example of Reverse proxy test type in the JetBrains/intellij-community repository (JUnit3) using the result evaluation via method name.
   • By internal object state - Example of Reverse proxy test type in the openjdk/client repository (JUnit3) using the result evaluation via internal state of the object.
3. Multiple test execution - Example of Multiple test execution in the jsfunit/jsfunit repository (JUnit3).
4. Customized testing solutions:
   1. Calling methods one by one
   2. Calling methods according to input data
   3. Helper function that returns an array of test cases
   4. Iterating values of enum
   5. Calling constructor
   6. Using @Test annotation
   7. Using own framework

Acknowledgements

This work was supported by project VEGA No. 1/0762/19: Interactive pattern-driven language development.