Test Planning

A structured test plan

Much of the testing we do is exploratory, especially with the website audits we carry out, as these are designed to be exploratory and unplanned.

However, there are many other projects that do require a more structured test planning phase before the actual testing begins.

Putting together a test plan can be extremely beneficial to the project, especially if conducted early on, as it helps to clarify how some functionality is intended to work, what constitutes a pass or fail and ask questions about ambiguous aspects or areas that don’t seem quite right.

Having a test plan also means that the testing phase can begin more smoothly, as much of the test preparation is already complete and test environments are in place.

Therefore, for more complex web builds and mobile apps, we would recommend undertaking the test planning phase first of all.

Test planning process

The test planning service usually follows the following process:

  1. We discuss the requirements for the testing with you and your team, either face to face or over Skype.
  2. We take specifications, wireframes, designs and any other documentation related to the requirements for the project.
  3. This documentation is digested and usually results in some queries and clarifications to be discussed.
  4. Test cases are written to cover the whole project and ensure that the test requirements are met.
  5. The final test plan is produced and signed off by you. Alterations can be made until you are 100% happy.
  6. Test cases are loaded into our test management software (or yours) ready for testing to begin.

Test planning software tools

We have experience of using the following test management tools:

  1. TestRail
  2. TestLodge
  3. CucumberStudio
  4. Targetprocess
  5. Zephyr

View Our Services

All of our testing services can have test planning added to them.