Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor test classes #161

Open
2 of 8 tasks
GLaDAP opened this issue Jun 7, 2022 · 1 comment
Open
2 of 8 tasks

Refactor test classes #161

GLaDAP opened this issue Jun 7, 2022 · 1 comment

Comments

@GLaDAP
Copy link
Member

GLaDAP commented Jun 7, 2022

Currently there are a lot of integration tests in the driver, but the parts tested are not clear and the expected results are not always evident from the test title and assertion. Documenting the test classes can improve debugging, especially test classes with very similar titles

  • Document test classes
  • Separate integration and end-to-end tests away from unit tests
  • Mock functions where required with e.g. Mockito
  • Where possible make tests smaller
  • Split tests in separate classes based on what functionality is tested so tests can be executed in parallel in CircleCI
  • Use CircleCI workspaces to prevent double build of driver jar
  • Upgrade to junit5
  • Use parallel execution of tests to decrease build time
@GLaDAP
Copy link
Member Author

GLaDAP commented Sep 25, 2022

Properties file for parallel test execution added in #193, together with separate build and test steps in CI, where the tests are ran in parallel where possible. Some tests which where previously executed in a for-loop now use JUnit ParameterizedTest annotation, which enables checking individual test cases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants