Currently there are two tests classes that informs user about actual BouncyCastle and unlimited stregth cryptography availability:

org.jboss.wsf.test.CryptoCheckMain that informs about BC availibility during execution of test-utils module

org.jboss.wsf.test.CryptoHelper that provides hints for exceptions in security related tests.

But both only recognize BouncyCastleProvider installed within security providers while JBossWS 5+ can also load BC provider from classpath. Thus the current mechanism can wrap actual exception in false warning on missing BC.

The proposal is to move printing info from test-utils to testsuite module to be printed where it actually matters.
The second proposal is to merge both classes and also detect the BC on test classpath.