Skip to main content

Exploratory Testing in Agile

Exploratory testing plays an important role in Agile environment due to limited time available and limited details of the user stories. To get the best results out of exploratory testing, it should be combined with other experience based testing techniques.
Some of the important features of exploratory testing in agile are:

  • Test design and execution take place at the same time guided by prepared Test Charter
  • The result of most recent tests are used to guide the next tests.
  • As mentioned earlier, it is combined with other experienced based testing in order to get the best results
  • It is a time boxed testing session and test charter provides the test conditions to cover. 
Test Charter

Test Charter is a statement of test objectives and test ideas (how to test) and mainly used in carrying out the exploratory testing. Below are some of the details included in preparing Test Charter:
  • Actor : the expected user of the system
  • Setup : the test environment set up needed to carry out exploratory testing
  • Data: test data to be used for testing
  • Priority: determines the importance of the charter based on the user story's priority and risk level associated with it.
  • Purpose: all the test conditions (what user is trying to achieve) 
  • Reference: all the related information sources
  • Activities: a list of ideas what to test
  • Notes: evaluation of the correct results by comparing actual and expected behavior, also known as oracle notes
  • Variations: alternative actions to complement the ideas given in activities 
Exploratory testing is managed by session based test which lasts from 1-2 hours (60-120 mins) uninterrupted testing. A typical session includes:
  1. Survey session which included the learning of how the system works.
  2. Analysis session includes the functionality and characteristics of the system under test
  3. Deep coverage session would have all the border cases and scenarios to have maximum coverage. 
Tester should have deep knowledge and understanding of the system. He can use heuristic guide to cover boundaries, functionalities, variations and interruptions. It is equally important to document the process like Test coverage, Notes, Risks, Issues and Actual behavior. 
This information would be used by stakeholders to understand the status of the tests performed during exploratory testing and also, if there were issues found during the test execution then this information would be used as a guide to understand the issue and help in replicating it. 

This is a summary of how exploratory testing works in Agile. Agile extension syllabus was referred before writing this article. 
Labels:

Comments

Post a Comment

Share your feedback

Popular posts from this blog

Remove Blanks from Excel Sheet when Excel doesn't recognize field as blank

This is one of the tricks which always helped me in removing the blank fields from an Excel sheet especially when the values are copied from other sources. I have added screenshots of a sample data to show you all the actions step by step. Here are the steps to remove blanks by using one of the special functions in excel: 1. Select your data-set (Select the column which has blank values) 2. Press F5 3. Select "Special". You will see below screen: 4.Select Blanks and click Ok as shown 5. All the blank fields are now selected, you can proceed and delete all of them by selecting "delete" from the home menu.   Here is the final result: I hope this was helpful. Share this with your colleagues and friends to help them out.
Post a Comment
Read more

Benefits of Early and Frequent Feedback in Agile development

One of the reasons why Agile is preferred over traditional development method is "Early and Frequent Customer Feedback". This is not only helps customer to get what he wants but also helps development team to understand the requirement better. There is no room for misunderstandings and delays. so no BAD CUSTOMER SERVICE! In this post, I am going to discuss about some of the major benefits of early and frequent feedback in Agile. One way to get the early feedback is "CI" or Continuous Integration. There are many tools available in the market like Jenkins which help in running automated tests when a change is introduced in the build and give the feedback on the build performance or quality. Below are some of the advantages of early and frequent feedback: Early and regular feedback helps in clearing out the misunderstanding of the requirements. Unlike in traditional method, fixing the issues or requirements change is a lot less expensive. Customer get to see the...
Post a Comment
Read more

Role of a Tester in an Agile Team

Tester in agile is no different from that of traditional tester but in agile, he has to play multiple roles apart from just testing the software. In this post, we are going to discuss about the role of a tester in a project following a scrum life cycle. To make a project successful, testing plays a vital role. In agile, the main idea is whole team approach where testers, developers and business representatives work together as a team. Below are some of the main roles or best practices followed by team members in an agile (Scrum) environment: Cross-Functional: Every team has team members with a specific skill set which they bring to the table. The team work together on Test strategy, Test plan, Test execution and evaluation. Quality is a shared responsibility.  Self-Organizing : There are no leads in Agile. Team is self organized, meaning every team member knows and understands his responsibility and work accordingly.  Co-located : In most of the cases, testers, de...
Post a Comment
Read more