Echtzeitsysteme / Echtzeitsysteme/iflye
Refactor inherited test cases (e.g., VnePmMigration)
- Dominant language
- Java
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently, there are various test classes that inherit a super test class and just overwrite the method to create a new algorithm instance to test. As this is a bad coding style, one may refactor the test cases to parametrized tests to remove the high number of classes for each test case.
Example file: https://github.com/maxkratz/iflye/blob/1bc84da8d29f8ef0b6f89b848bca2d90db743fe0/test.suite/src/test/algorithms/pm/migration/VnePmMdvneAlgorithmMigrationTotalCommunicationCostATest.java#L21
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with test.suite/src/test/algorithms/pm/migration/VnePmMdvneAlgorithmMigrationTotalCommunicationCostATest.java and inspect its inherited superclass and related migration test classes. Identify the repeated subclasses that only create a different algorithm instance, then review how Java parameterized tests can represent those cases. Done means the redundant test classes are removed or consolidated and the migration tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100