-
Notifications
You must be signed in to change notification settings - Fork 0
Improvements of Integration-Tests #104
Copy link
Copy link
Open
Labels
feature requestThe Issue requests a new featureThe Issue requests a new featurehelp wantedWhoever feels comftable with this kind of Issue should help the owner of this IssueWhoever feels comftable with this kind of Issue should help the owner of this IssueimportantThis Issue has do be done by a direct contributorThis Issue has do be done by a direct contributor
Milestone
Description
Metadata
Metadata
Assignees
Labels
feature requestThe Issue requests a new featureThe Issue requests a new featurehelp wantedWhoever feels comftable with this kind of Issue should help the owner of this IssueWhoever feels comftable with this kind of Issue should help the owner of this IssueimportantThis Issue has do be done by a direct contributorThis Issue has do be done by a direct contributor
Feature-Request-Checklist
Please make sure the feature you are requesting has not already been reported!
If your checklist is not fully ticked, please try to complete it such that it does.
If you are uncertain of specific parts, please do not propose a new feature request.
The following is a template to help you state the request clearly.
Description
The existing Integration-Tests should be integrated into JUnit and be annotated with @ignore. Then, the test should be runnable to allow for a simple "run and test".
The reason
As of bug #101, it became prevelent that the Integration-Tests are insufficient for verrifying a bug-fix of a not Unit-Testable bug. Making those Integration-Tests simple to start and read wether the bugfix was done correctly, should help clarifying Integration-Tests.
Example
Simple test-classes. Sorry, i can't think of a good to read example here