Agile or fragile development? You still need to test!
The other day a governmental organization rang me to ask if Rati
RFT is a tool that testers use for automated regression testing. It heavily depends on the GUI elements for object recognition. Though RFT supports only a limited set of GUI elements, it does cover the most widely spread GUI elements on Windows and Linux. See the list in Supp
Those were the days
In the days of mainframe COBOL, the developers first hit their keyboards to put in the test set. For example, you coded a numerical field of three positions that need input from the user. Now you compare the output that you expect to the actual output when you run your program.
So before you typed in the first line of code, “IDENTIFICATION DIVISION,” into your virtual interface editor, you already had your test set ready.
Just like in the old days, you might want to think ahead. So before you design your GUI, first figure out whether you can actually use your existing testing tools to test the new GUI. Otherwise, you might encounter the same deadlock that the governmental organization did. In agile development, a scrum meeting might be an appropriate platform to exchange information between developers and testers. I look back to the days of mainframe COBOL with nostalgia.
Hopefully this blog helps you to think about the development lifecycle of your software, especially how you allocate functional regression testing. If you'd like to discuss this further, leave a comment or connect with me on Twitter @GunangWaney.