As we move forward in to 2014, it’s time once again to look at upcoming trends in quality assurance automation testing. We’ve seen an increase in the demand for various kinds of automation testing. This includes regression automation, load testing, performance testing, and unit testing. In general, automation testing is just what it sounds like: you have some manual tests, you want them executed whenever you want, but not by a human or monkey.
This sounds easy enough, so why don’t people use this more often? For starters, you preferably need a STABLE CODE BASE! Things like field names should be nailed down before you start thinking about automation, and if available, the manual test you are basing your automation on should have been executed and passed. Now you may be wondering, what about performance testing; why do I need a manual test case for that? Well, someone out there needs to know what pages/actions they are performance testing. Linking the automated test to a manual test helps the next person who runs the test know what they are actually doing. This link also helps to update the test to keep it relevant.
Unfortunately, you don’t always get what you want. When using Agile, you might not have a steady code base. Your client might just want some record and playback test cases (where you run the test manually while recording with whatever tool the client requires, then click play), or the client could want test cases completely coded from scratch (giving you a greater amount of control, but consuming more time).
Both the technical and non-technical have an increasingly large place in the technology world. No matter how vast or limited your coding knowledge may be, there are options for you, from QTP that uses VBScript, to QALoad with its C++, to Visual Studio with C#, or whatever else your heart desires.
As the demand for shorter timelines increases, developers will need to create their own coded unit tests. These tests may add more time on the development side, but, when done correctly, can add a high amount of value and save time on the QA side. If you are using Visual Studio for testing as well as development, these handy little unit tests can then be transferred into load or performance tests.
We are moving forward into a time when everyone will have to learn automation testing in some capacity; it is not going to be exclusive to QA or the Consultant level. No matter your career level, coding knowledge, or desired field alignment, automation testing of some sort will be in your future.