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
You could automate simple GUI tests specified in the integration tests by writing macros. Simple things like verifying that an error message pops up, when the user tries to run a plugin with a wrong kind of image. For example "Verify that the ConnectivityWrapper plugin shows an error message if the user tries to run it with a non binary image".
There might be a way to automate the running of these test macros, but even having them around as manually runnable files would help in testing that everything still works after changes.
The text was updated successfully, but these errors were encountered:
I've learned how to automate most tests in JUnit with the help of Mockito the mocking framework. It's more convenient to run these automatically in the IDE or with Maven instead of launching macros.
You could automate simple GUI tests specified in the integration tests by writing macros. Simple things like verifying that an error message pops up, when the user tries to run a plugin with a wrong kind of image. For example "Verify that the ConnectivityWrapper plugin shows an error message if the user tries to run it with a non binary image".
There might be a way to automate the running of these test macros, but even having them around as manually runnable files would help in testing that everything still works after changes.
The text was updated successfully, but these errors were encountered: