I'm not sure what you are showing me. It looks like a filtered view of the actual test output.
The tests within the source distribution for the WS-Sec callout as well as the XML DSIG callout include tests for a variety of different failure cases, in which the callout code throws exceptions. This might be, missing arguments, invalid arguments, inconsistent arguments, and so on. One good example of this is "private-key resolves to an empty string". For signing, the configuration of the callout must provide a private key. One possible configuration error is that the configuration specifies a private-key property that points to a context variable that does not exist. There is a test that verifies that the callout handles this configuration error gracefully: it throws a fault (exception), and returns a reasonable, human readable string that explains the error. There are many other examples.
For diagnostic purposes, the test code may print out notice of the exceptions in those error cases. In some cases the test code prints out stack traces! None of those things are indications of test failures.
I guess you have a log scanner that is looking in the full test output for keywords like "Exception" and "error". That's not going to give you an accurate assessment of the success or failure of the test run, with these callouts. The tests for these callouts are not designed with the convention that the words "Exception" and "error" must never appear in the test log. I advise you to look at the summary of the test run, which is at the bottom of the output. It will look something like this:
...
[INFO] Tests run: 53, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.345 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 53, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-dependencies) @ apigee-wssecdsig ---
...
[INFO]
[INFO] --- maven-jar-plugin:3.2.0:jar (default-jar) @ apigee-wssecdsig ---
[INFO] Building jar: /Users/dchiesa/dev/java/callouts/wssec-signature-2/callout/target/apigee-wssecdsig-20220204.jar
[INFO]
[INFO] --- maven-antrun-plugin:1.3:run (ant2) @ apigee-wssecdsig ---
[INFO] Executing tasks
[copy] Copying 1 file to /Users/dchiesa/dev/java/callouts/wssec-signature-2/bundle/apiproxy/resources/java
[INFO] Executed tasks
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.479 s
[INFO] Finished at: 2022-02-09T06:47:45-08:00
[INFO] ------------------------------------------------------------------------
You can see the summary line that tells you how many tests have run, how many have failed, how many were skipped, etc.
For a successful build and test run, you will see 0 failures, 0 errors, 0 skipped, and a non-zero number of tests run. In this case it's over 50 test cases. That's indicates a successful run, even though there might have been exceptions logged during the test run.
LinkedIn
Twitter
