now that we have identified the fact that automation is required let’s have a look at the approaches already available.
- Code driven testing
- Graphical interface testing (GUI)
The code driven testing involves testing the classes, modules and/or libraries.
The graphical interface testing involves the emulation of keyboard and mouse actions. The output is visible on the screen.
How to chose between one and the other?
This question arises because the GUI projects are composed of code but not all the applications have a GUI.
If the project’s code exposure through visual feedback for both the configuration data (Admin) , manipulation feedback (Frontend) and it’s scope is to facilitate the actions of the visitors, the GUI only approach is enough.
If the configuration data is updated through a file (.tsv/.csv etc), some code driven testing is necessary for the input scenarios.
If all the project is an API, for instance, or its scope is to connect two systems, code driven testing is sufficient.
Based on this article we know for sure which way we should head with our automation process.