I recently updated JMockit from 1.16 to 1.19 and ran all test suites I had prepared for my previously reported issues and all passed correctly.
But yesterday one of my developers reported a failure on her old tests cases which used to pass. Wondering what might have went wrong, I finally restored JMockit 1.16 to find out that the test pass now.
This was very weird exception to spot and it was very hard to reproduce in another test case. I had to work on it for few hours before being able to create such combination with simplified version of our complex hierarchy of generic objects.
I also check with other versions and found out that the issue manifests itself from update 1.17 onward.
I recently updated JMockit from 1.16 to 1.19 and ran all test suites I had prepared for my previously reported issues and all passed correctly.
But yesterday one of my developers reported a failure on her old tests cases which used to pass. Wondering what might have went wrong, I finally restored JMockit 1.16 to find out that the test pass now.
This was very weird exception to spot and it was very hard to reproduce in another test case. I had to work on it for few hours before being able to create such combination with simplified version of our complex hierarchy of generic objects.
I also check with other versions and found out that the issue manifests itself from update 1.17 onward.
Here is the test case
Here is the exception stack trace of running it with 1.17+:
Our test environment:
The text was updated successfully, but these errors were encountered: