Skip to content
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

Assertion results output #115

Open
rboitsg opened this issue May 2, 2023 · 0 comments
Open

Assertion results output #115

rboitsg opened this issue May 2, 2023 · 0 comments

Comments

@rboitsg
Copy link

rboitsg commented May 2, 2023

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:

  <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'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant