Using a Combination of Scripted, Automated and Exploratory Testing for Optimum QA Coverage

Most test teams today are struggling to find better ways to handle their testing. With the advent of Agile in our software development processes, teams are perennially under pressure to provide faster releases without lowering their standards of quality. This, in turn, adds load on the in-house test teams to ensure finding more and crucial issues and to prevent defect leakage. For this reason, testers look at strategies and practices that can help them achieve their goals and add more value to the product’s quality.

In my opinion as a hands-on agile tester, there is no single silver bullet to quality, but a combination of different types and approaches to testing that can help us get closer to our quality goals. Test teams need to strategize and plan the usage of a combination of scripted tests, automated tests as well as exploratory tests for achieving an optimum coverage and best quality software.

Here is my latest article for PractiTest QA Learning Centre where I discuss the need to have a combination of scripted, automated as well as exploratory tests for an optimum QA coverage–

https://www.practitest.com/qa-learningcenter/thank-you/exploratory-testing-optimum-qa-coverage/ 

Scripted Tests

When we look at the typical test approach, it begins with test scripting and designing tests as per software functionality. These are created using requirement analysis and test design techniques and also using common sense and skills by our skilled testers. These scripted tests form the starting point of testing a new feature, change or addition in the software.

Automated Testing

In addition to running the scripted tests manually, testers also rely on automated tests. These tests are scripted using various test automation tools and test automation, i.e. ability to write these automated test scripts is, thus, a much-wanted skill nowadays for all test professionals. The ability to run some tests using automated scripts helps repeatability and saves a lot of time and effort on part of the test teams. But most importantly, by automating the drudgery away, it saves the tester from repeated manual laborious tests and frees up their time for more creative thinking and exploration around the application.

Exploratory Testing

Exploration of software is basically looking at the feature/functionality/change and overall behavior from a learning as well as a critical standpoint. Exploratory Testing is a crucial aspect of software testing, which almost every tester performs knowingly or subconsciously.

Cem Kaner coined the term Exploratory Testing in his book “Testing Computer Software” and described it as:

“Simultaneous test design, test execution and learning with an emphasis on learning”

https://www.practitest.com/qa-learningcenter/thank-you/exploratory-testing-optimum-qa-coverage/ 

Read More »

My talk at the UNICOM World Quality Summit 2017, Bangalore

Hello Friends,

I was recently invited to speak at the World Quality Summit 2017 organised by UNICOM at The Leela Palace, Bangalore. The event saw attendees from many teams from Pune, Gurgaon and the city itself who participated in the Quality Olympiad. It was a good mix of audience and lots of interesting talks and discussions during the sessions.

I spoke on the Practical risks in Agile teams and Ways how testers can help build-in continuous quality in Agile projects.It was a great experience, met some great people and enthusiastic teams and got awarded the Thought leadership Certificate by UNICOM!

Check it out!

 

Cheers

Nishi

Practical Session on Playing Innovation Games @MetricStream

Agile needs continuous improvement and innovation , and we are striving for the same at my new workplace MetricStream, Bangalore. As a part of that, I was invited to conduct a session on some practical and easily adoptable agile practices.
Well what better than Innovation Games for that !
So we went ahead and did a 3-part practical training exercise session wherein not only did we learn about the Agile workflow , the basics on innovation games and how they fit into Agile , but also conducted practical group exercises with sample scenarios and user stories.

It was a great experience and received quite well. The participants were encouraged to take back the learning to their own scrum teams and try out the fun and quick games for conducting various Agile ceremonies.

Here is a glimpse into the training room :

Playing Innovation Games
Playing Innovation Games

Playing Innovation Games
Playing Innovation Games

Playing Innovation Games
Playing Innovation Games

Playing Innovation Games
Playing Innovation Games

Cheers,

Nishi