Open BrynCooke opened 6 years ago
When using hamcrest via remote junit runners there may be issues because AssumptionViolatedException stores fields that may not be serializable.
If the the message was created in the constructor rather than in getMessage then this could be avoided.
Hi @BrynCooke , that does seem like a significant barrier to running tests remotely. That class is part of the junit repository - would you please consider opening this issue there instead?
junit
https://github.com/junit-team/junit5/
When using hamcrest via remote junit runners there may be issues because AssumptionViolatedException stores fields that may not be serializable.
If the the message was created in the constructor rather than in getMessage then this could be avoided.