E.A.T approach for achieving software quality

Combining Exploratory and Automated Testing approaches

Finding the bugs in a software earlier can save time and money for a company. If there is fault slip through, then identifying the root case and doing respective changes in development can more cause time and money. Every tester, team and company targets to release a bug free product to it’s stakeholders — though it is a big challenge and developing a test strategy depends on project’s test needs and most importantly company’s quality mindset. Various testing approaches are useful for different testing levels.

In this post, I would like to propose a new term “E.A.T” — combining Exploratory and Automated Testing approaches. Here is what I think about it; Continue reading

6 Benefits of using Exploratory Testing (ET) approach

Exploratory Testing
Bug hunt with Exploratory Testing

Exploratory Testing (ET) approach has gained focus and popularity in recent years. There are more studies and has received professional attention from industry too. I think, ET approach acts like a power to a tester, but power comes with responsibility as well, it’s a great opportunity and freedom for tester to explore and identify areas for quality improvement. Tester has the advantage to demonstrate own skill set, knowledge and experience from different perspectives and help improve the quality of system under test.

You as a curious tester have been using exploratory approach unconsciously in your test activities, just give it a thought.

ET has been known as simultaneous learning, test design, test execution and test analysis — a way to define this approach. Over time, the definition of ET has emerged from an error checking technique to a defined testing approach. You can find all the definitions since 1988 on James Bach blog.

From my personal experience, observations and discussion with ET practitioners,  I would like to highlight 6 benefits of using this approach, even though there are many more. These benefits are related directly or indirectly to testers, teams and management. Continue reading