GETTING STARTED: AS A PROJECT LEAD & TEST WRITER

Easily execute test scripts, record progress in a central location, and export the results of test sessions to share with the team. Know exactly what needs to be tested and how.

1.

Create an account and add your project to Verfolio. You can add multiple projects for the same software or app, or make a single project for the entire app. It’s up to you.

2.

Add test cases to your project.

Test cases are similar to use cases or user stories in nature. However, a single test case might cover multiple use cases or user stories. The goal is to make the test cases specific enough to be effective and thorough but not so specific as to be inefficient.

Add steps to your test cases. Each step is an action the tester should take and the expected outcome they will test for.

3.

Invite the other team members to join your project. Share GETTING STARTED: AS A TESTER with them to help them get started.
Inviting anyone who will be running the tests is of course needed. However, don’t forget to invite other roles too. Knowing what test scripts will be executed and what is expected can be helpful to everyone. Don’t worry, you can have as many free accounts included in your project as you like.

DELIVERABLES-DRIVEN PROJECTION TESTING

Using the test cases for projection testing is very powerful. Done right, it can actually serve as a progress report for your stakeholders and clients. To do this:

  1. Take all the deliverables from the project SoW (statement of work) and create test cases out of them.
  2. Share those SoW-based test cases with the client or stakeholders to build consensus.
  3. With each scrum cycle or agile iteration run the full set of projection tests.

At first they will all fail and the progress bar in your reports will be 100% red. However, each iteration will see this progress bar turn green over time, giving the team a gauge of where the project stands.