By Lakshminarasimha Manjunatha Mohan
At SPAN, we have been testing a variety of software since many years. Every software that we have tested has been very different and challenging because the context of testing has been different. Context drives the testing and this makes testing problems complex and different to address, every time. The testing context includes the technology stack, team, stakeholders (including the customer), available resources, artifacts, time, environment, etc. Here is a short collection of some of the testing stories that illustrate how we have efficiently handled different testing problems. For the customers and prospects, these stories illustrate how we test software at SPAN and for the learners; each of these stories is a gem teaching a lesson.
Story 1 - Collaboration and Team Work, Leading to Success in Time-Constrained Projects with No Time Commitment from the Customer
Context:
A Swedish product company had engaged SPAN to execute their flagship Content Management and Web Publishing product testing. The scope was to test the functionality of the web and APIs on a host of operating systems and browser combinations. It was a collaborated product development team with customer developers at Stockholm, Sweden and testing team at Bangalore, India. SPAN was being evaluated for its delivery capabilities during the first 4 months.
Description:
We started the project by going through the testing trail – Bugs, Product and the User. The first problem to solve was to test and change the status of 1000+ bugs that were logged by developers with a constraint that there was no time for the development team or anyone with the knowledge of the product to clarify the questions from testers. The challenge was to understand the bugs that were not described well enough. To add to these, there were several bugs that were not updated, but resolved in the application.
At this juncture, we ran weekly sprints in SCRUM, testing/learning the product in an exploratory fashion and testing the bugs. We did receive many questions during the course that were listed and further discussed internally. It was a classic display of team work and collaboration wherein, everyone in the team participated and discussed about the questions and further explored to find answers to the questions, helping one another. This continued in iterations and finally we had only 13 bugs/questions left for clarification by customer. Efficiently, we had managed to pass the evaluation and providing value to the customer even when there was limited documentation available and limited facilitation time by the customer.
The highly collaborated team work helped in bringing cohesion in the team and also helped each other find answers to the questions. The context driven exploratory testing approach helped the team to gain good understanding of the system even when there was little support from outside and not much documentation. Further, the customer started seeing the value of our work and automatically, we became their part of the team.
Read Story 2 at http://spansys.blogspot.in/2015/02/testing-stories-from-spans-trenches_11.html
At this juncture, we ran weekly sprints in SCRUM, testing/learning the product in an exploratory fashion and testing the bugs. We did receive many questions during the course that were listed and further discussed internally. It was a classic display of team work and collaboration wherein, everyone in the team participated and discussed about the questions and further explored to find answers to the questions, helping one another. This continued in iterations and finally we had only 13 bugs/questions left for clarification by customer. Efficiently, we had managed to pass the evaluation and providing value to the customer even when there was limited documentation available and limited facilitation time by the customer.
Read Story 2 at http://spansys.blogspot.in/2015/02/testing-stories-from-spans-trenches_11.html
No comments:
Post a Comment