Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
The focus always seems to be on short stories and then the code that goes with them tends to have units tests.
What other areas or levels should I be testing in?
The context is for SaS (Software as a Service) applications being developed in an Agile environment using a variety of Scrum and Kanban techniques.
During each iteration for each story I like to-do the following:
Suggest reads:
Unit testing is a great way to test code with specific endpoint values and compare them with expected results, but there are many things that unit testing cannot cover. Unit tests provide you with a linear test, for the software. Automation should cover a more broad approach to what the software actually does. Agile is a difficult space to implement automation, and it needs to have ample time to be set up. After the framework is up and running, you can add tests in your suite sprint-by-sprint to cover the material developed. So to answer your question, other areas for automation include a wide variety of things. I would recommend you speak to your Project Manager to see what they expect from your automation. Currently for me I write automation for:
These are the items that I am responsible for, and this is what my testing encompasses.
