test01_3GPPMode Failure expected:<...tAfter: Thu Jan 16 1[2:38:24 CET] 2014> but was:<...tAfter: Thu Jan 16 1[1:38:24 UTC] 2014>
junit.framework.AssertionFailedError: expected:<...tAfter: Thu Jan 16 1[2:38:24 CET] 2014> but was:<...tAfter: Thu Jan 16 1[1:38:24 UTC] 2014>
Failure happens when server uses UTC, since client message is hard coded to
String expectedErrMsg = "The certificate attached to the PKIMessage in the extraCert field is not valid - Could not validate certificate: NotAfter: Thu Jan 16 12:38:24 CET 2014";
Tests would also be sensitive to Locale mismatch.
- A nice solution would catch this exception and transform it into something more deterministic.
- A descent/semi-robust solution (ignoring Locale) would conclude that the error message is good enough if it begins with the string up to an including "... NotAfter:"
- A less nice solution might be to create the client side version of the error message of the test in the same way as we expect the server to do it.