I have just a general question about automated testing. My managers want to switch over to automated testing but I am not sure if it necessary. I am currently working on a cost analysis so I will see how that works out. We create web applications for a bank and we just test the functionality but they want to automate this testing.
So I was just wondering in what types of situations do you use automated testing?
If it needs testing - Test it
If it need testing again - document it.
If it need testing again - Automate it.
A quote from one of my mentors.
Apart from that you may need to change your mind set from your current Manual Test or Automated test to the more successful Test automation for manual testers.
To take a simple example in a banking application you need to add a deposit to an account the tester looks up the current balance and writes it on the back of an envelope, invents a transaction and enters this value write a plus sign beside the value previously written and writes the recently entered value, these are added together manually and check against the result produce in the application.
A small degree of automation would be to proved the tester with a calculator to perform the addition. Another level would be to provide a spreadsheet where several scenarios could be stored and re used.
Note that we have not done any automated testing just adding test automation.
The next level is to find a tool to enter the values in your spread sheet into you application read back the results compare to the expected values, write an appropriate report raise any issues. Whilst this is sometimes called automated testing it is still just test automation.
By the time you have developed and written all you automation your testers could have tested the application about 3 or 4 times
By the time the automation has been implemented it will replicate the effort of 3 or 4 test in the time it used to take to do one.
(not to scale)