-
Notifications
You must be signed in to change notification settings - Fork 40
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
Implemented LineRange-class and improved overall code-coverage #30
Implemented LineRange-class and improved overall code-coverage #30
Conversation
…or test-cases as the get()-calls for the artificially constructed objects will always return a value)
* | ||
* @author Jannik Treichel | ||
*/ | ||
class CoverageParserTest { |
Check notice
Code scanning / CodeQL
Unused classes and interfaces Note test
|
||
import static edu.hm.hafner.coverage.assertions.Assertions.*; | ||
|
||
class MutationStatusTest { |
Check notice
Code scanning / CodeQL
Unused classes and interfaces Note test
* These might also be tested by adding additional asserts | ||
* in the tests for the {@link Node} class --> {@link NodeTest}. | ||
*/ | ||
class MutationTest { |
Check notice
Code scanning / CodeQL
Unused classes and interfaces Note test
Thanks! |
As requested, these are tests and implementations from some of the exercises during the testing-lecture (summer-semester 2023, University of Applied Sciences Munich):
A LineRange-class was implemented for grouping coverage-information for consecutive lines-of-code.
Various new tests improve overall line-, branch- and mutation-coverage for the project.
Testing done
All tests (old and new) run successfully on my local system (based on current state of the main-branch in the official coverage-model-repository).
Submitter checklist