Skallesh

You did not understand my point.  Calling assertContainsNoMatch can easily pass for the wrong reasons.  A simple typo in your message or a simple string change by the developers will make assertContainsNoMatch always pass.  My suggestion was to use clienttasks.getCurrentEntitlementCertFiles().size() before and after the call to clienttasks.importCertificate(path); to make sure the number of entitlements remains the same on the system.  I think that is much more reliable than asserting a message to stderr (especially if the developer changes it to write to stdout - you'll never catch the change).