First of all, let me introduce myself. I’m Gautam, the new Test Lead at Foradian. The intention of this article is to let you all know about the way testing has changed at Foradian over the past few months and the benefits we have derived out of it. This article would be of interest to all those who have got bored of the Conventional Approach to Testing i.e. maintain elaborate test cases, execute them and mark them as “Pass/Fail”, and repeat the test execution over multiple cycles in a monotonous manner! Have you come across testers who would say “Testing is so boring”? If yes, they are right, because the approach they used to test might be boring! Making the testing activity as boring or interesting is completely in tester’s control. Do read on to find out how our Testing Team has benefited by using the Exploratory Testing Approach rather than the Conventional Approach. By the way, it feels glad to inform you that our Test Team has grown in size from 2 to 5!
Here’s the feedback from a couple of our testers!
Sreeshanth, our Senior Tester says:
I was unaware of the Exploratory Testing approach when I began my career. I got a taste of it in July 2014. I learnt that Exploratory Testing refers to simultaneous test design, test execution and reporting. In this, the tester has complete freedom to test the application of interest. In my opinion, the earlier test approach we followed was more time consuming than the current one. Previously, after completion of the development process, we directly started testing by creating a document, which was also shared with the developers. First we tested in the dev’s local server, and once all issues were fixed, we used to begin testing in the test server.
With the use of Exploratory Testing approach, a lot has changed. When we get a new feature to test, we won’t know much about the behavior. So initially, we go through the SDS and SRS to get a fair idea about the feature. Later we brainstorm using mind maps. I felt mind mapping is the perfect tool to brainstorm test ideas and execute them, gradually evolving our test ideas while testing. This way, testing becomes interesting and empowers the creative side of testing, which feels rewarding too. After this, we create lean test design (Test ideas and scenarios without elaborate steps to be performed) in excel format and share it with the developers. The important thing is, we start the testing process even before the development begins, which is also helpful for developers to understand the feature from an end user’s perspective. After a feature is developed, we execute tests in the test environment and report the results. With this approach, we could test faster and with more creativity.
Ali, another Senior Tester says:
I would consider the change in the test approach a welcome change, when compared to the methods used by my previous employers. From what I understand, the earlier approaches were tedious and time consuming. They sucked the fun out of testing. I believe it is important for the tester to enjoy his testing activities. Conventional test approach limited the exposure to practical scenarios that would be encountered by the user. Since the tests were scripted and static, it also lead to limited expectations.
With the use of ET, we do not document the expected results, because there could be many and it’s up to the tester to identify them while testing. ET provides personal freedom since testing is not defined in advance. I found it to be intellectually stimulating. The use of mind maps enables me to make note of the important areas to be covered during testing. I remember having used it during my early days in Foradian for testing a feature along with Gautam. Exploring one module or scenario opened doors to many other possible scenarios. ET gives better coverage too. It is important to find the critical defects in a timely manner and ET helped in identifying the critical defects very quickly. Usually with ET, there is the risk of not being able to recreate the scenario that led to the issue in the exact manner, but this is taken care by the lean test documentation approach we follow. Mind maps and test reports are maintained for documentation.
Our New Test Approach
Involving the Testing Team in the UX Design phase itself, so that UI/UX bugs could be identified well in advance, rather than during testing. We do the Test Design as soon as the UI prototypes are available, and add more tests during the Exploratory Testing phase.
- Implementation of the Test Strategy mind map for every feature to be tested, lists the probable areas impacted by the feature. This list actually expands our test ideas to achieve better test coverage. This would also help our developers to know and handle impacted areas across modules.
- Following the Lean Test Documentation (Flexible excel template for listing only the test ideas and test scenarios, excluding elaborate test steps, and marking the test execution results against them) approach helps us devote less time for Test Design and more time for Exploratory Testing.
Here’s a sample Test Strategy mind map for your reference!
To conclude with, we are committed to test your favorite Fedena much better, resulting in minimal bugs which hardly bug you, thereby giving you an enhanced user experience! Team Foradian is thankful to you for your unprecedented support and cooperation.
The article is written by:
Gautam M S
“Gautam doesn’t breathe air, he breathes testing instead. He is a disciple of the Context Driven Testing community and testing is his way of living. You can’t convince him without logic! He believes testing is a scientific way of analyzing things at hand!”
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?