We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When testing an EO, usually a basic setup have to be made in order to test an EO:
private EO eo;
@before pubic void setup() { eo = EO.createEO(ec); }
The @undertest annotation could be used to reduce the amount of boilerplate code.
@undertest private EO eo;
The MockEditingContext and the TemporaryEditingContext rules creates and inserts the EO automagically.
The annotation is also useful as a sanity check. Unit tests usually will have only one field annotated with @undertest.
The text was updated successfully, but these errors were encountered:
Suport to @undertest annotation (issues #10). Still needs a refactoring.
ca886bf
Suport to @undertest annotation (issues hprange#10). Still needs a re…
d60d255
…factoring.
Updating the javadoc documentation to reflect the new features (issue #…
5fef202
…10)
Make the annotation processing more generic (issue #10)
0d8f7e8
hprange
No branches or pull requests
When testing an EO, usually a basic setup have to be made in order to test an EO:
private EO eo;
@before
pubic void setup() {
eo = EO.createEO(ec);
}
The @undertest annotation could be used to reduce the amount of boilerplate code.
@undertest private EO eo;
The MockEditingContext and the TemporaryEditingContext rules creates and inserts the EO automagically.
The annotation is also useful as a sanity check. Unit tests usually will have only one field annotated with @undertest.
The text was updated successfully, but these errors were encountered: