You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BTW a very simple thing to do is to do a static import for import static org.junit.jupiter.api.Assertions.*;. This removes all the Assert. prefixes and make the code more readable too. :)
BTW a very simple thing to do is to do a static import for import static org.junit.jupiter.api.Assertions.*;. This removes all the Assert. prefixes and make the code more readable too. :)
This issue comes from Spoon if I remember. A release is announced on the 11th, February. I'm gonna bump the version used by DSpot.
Couldn't dspot decide to not add the second part since calling the getters has no side effects?
It could. For now, DSpot does not distinguish the "type" of statement between the sequences of assertions. If there is something, (invocation, local variables, etc...) It should generate the second sequence.
Example of generated test (showing a screenshot that shows in light grey what can be removed)
The text was updated successfully, but these errors were encountered: