| commit | 6c5932ac952a1b3d335fa7217f3b54799321dd95 | [log] [tgz] |
|---|---|---|
| author | Allon Mureinik <allon@synopsys.com> | Wed Oct 10 19:45:44 2018 +0300 |
| committer | Allon Mureinik <allon@synopsys.com> | Wed Oct 10 21:27:11 2018 +0300 |
| tree | a89249813c2c8f5ef64fa712ec6d1fcfb73a86e8 | |
| parent | a59d8f1b4504e30b36c7a22ef2e087cbd98a7553 [diff] |
SCXML-284 Replace try-catch with assertThrows Use JUnit Jupiter's new mechanism of assertThrows instead of try-catch blocks in order to clean up the code and make it easier to follow. Since the questionable piece of code is now run inside a lambda and is caught by asserThrows itself, there's no need to declare these exceptions in the throws clause of the mehod declarations, and they were cleaned up to avoid adding compiler warnings.