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 using --check-assertions I can see the successfull and failed assertions in console/stdout. Assertions run: 44, Assertions failed: 15
--check-assertions
Assertions run: 44, Assertions failed: 15
An assertion may define a message for what is being tested:
<a:assertion report-doc="MyEvilFile-report.xml" test="/rep:report/rep:assessment/rep:accept"> Report has status accept </a:assertion>
Where can I find this text?
Use Case: It is difficult to track down failed assertions if the number of assertions is more than one.
For reference, I call the KoSIT Validator within Ant like this:
[apply] Executing 'java' with arguments: [apply] '-jar' [apply] 'lib/validationtool-1.5.0-standalone.jar' [apply] '-h' [apply] '-s' [apply] 'build/config/scenarios.xml' [apply] '-r' [apply] 'build/config' [apply] '--check-assertions' [apply] 'build/test/assertions.xml' [apply] '-o' [apply] 'build/test/report/' [apply] 'MyEvilFile.xml'
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using
--check-assertions
I can see the successfull and failed assertions in console/stdout.Assertions run: 44, Assertions failed: 15
An assertion may define a message for what is being tested:
Where can I find this text?
Use Case:
It is difficult to track down failed assertions if the number of assertions is more than one.
For reference, I call the KoSIT Validator within Ant like this:
The text was updated successfully, but these errors were encountered: