Agile testing tooled by XStudio

Summary

Introduction

Exploratory testing

Exploratory Testing practice and tools associated support perfectly lean development. One of the most common definition for Exploratory Testing (ET) is 'simultaneous learning, test design, and test execution'.

You can also see that as Exploration and Experimentation.

In agile projects, you explore and experiment during Sprints and with any solution increment.

• Developers not only unit test their code and documentation, but also ensure that the solution meets the acceptance critera defined in each User Story.
• Business Analysts and Users test to validate that the solution fully meets the needs.
• Dedicated testers test to ensure that the solution is and remains 'rock solid'

Because you do not really know when you are done with your feature set, you need to be able to test it, without investing too much effort, too soon, in scripted tests.

Still, XStudio provides you with an easy to use language (Procedure Description Natural Language or PDNL) that allows taking notes as you test and turn those automatically as scripted test.


Please refer to the Exploratory sessions in the User's Manual to learn about how to achieve this.

On-the-Spot test session

On-the-Spot test session allow fast feedback for agile projects.
You can immediately execute any single test, in its own test session.

Developers, business analysts, users can rapidly use existing tests or define new ones and verify those in order to make sure they succeed.

These tests are then usable in campaigns that address a larger set of features or requirements.

All such tests' runs are being managed in what we call the Playground Campaign. This makes it easy for all to see which tests are to be reusable and those that are still being verified.

Still, this is fully taken into account when asserting the quality of a release, product or requirement.


Please refer to the Run an individual chapter in the User's Manual to learn about how to achieve this.

Per User Story or Requirement micro-campaigns

Per User Story or Requirement micro-campaigns enable high quality incremental development.

In many agile projects, the 'Best' Practice is to associate several Tests to any single User Story, or more exactly to its Acceptance Criteria (AC).
This way you can check throughout the Sprint and after Sprint review that all AC are verified.
Then you can start incrementally adding more thorough tests (potentially using Exploratory Testing).

XStudio lets you easily select the tests you want to run by identifying those User Stories, Requirements or Specifications that matter for the test you want to conduct.

So you can decide to run a micro-campaign for 1 or 2 Users Stories that are highly dependent from a functional or technical standpoint.

Alternatively, you can gather a full Sprint of tests and run it as a verification step.


Please refer to the Create a campaign chapter in the User's Manual to learn about how to achieve this.

Per Defect micro-campaigns

Per Defect micro-campaigns ensure short delay fix cycle.

Sprint driven or flow driven agile development incrementally adds and improves features, but also addresses bugs and defects as early as possible.
Developers need to be able to re-test immediately for each fix without waiting for a tester or a user to be available.

XStudio allows you to select only those tests that discovered the bugs or defects you want to fix and verify. This is one event when traceability is a MUST.



Please refer to the Filtering from Bugs chapter in the User's Manual to learn about how to achieve this.