3 steps to help you clean your testing repository quickly! Today the most expensive resources are the human resources – your team – and by having many useless tests in your repository you are wasting their time!

1. Spring cleaning your testware
to help you clean
your testing
repository quickly3 steps
A mix of good and bad tests increases the chances a tester will
run a wrong testand miss partof the issues thata good test
would have detected quickly.
Today the most expensive resources are the human
resources – your team – and by having many useless tests
in your repository you are wasting their time!
You are wasting the time ittakes them to find the tests they
need to run.
You are making itharder for others to understand if they need
to create newtests or if they can re-use existing ones.
Sponsored By

2. Step1: Organize your testing repository
Organize your tests in a way that will help your
testers find them easier and faster.
If you are using any other test tool or even
Excel to manage your testing you should try to
create the most intuitive and simple
classification in your test tree, use a
convention that will let you manage test cases
and the rest of your test ware.
When choosing a convention, the most
intuitive one is usually based on your
application’s structure. Start from the products
or components, and then go down 2 or 3 levels
to Sub-Components, Features and even
Screens.
PractiTest provides a
pretty nice solution for
this in the form of our
Filter Tree, that let you
organize and catalog your
tests in multiple ways at
the same time,
automatically organizing
everything based on your
tests’ fields.
By the way
Step2: Mark your tests while you are
running them
Add a new field or parameter to your tests that each of
your testers can set when they are either running or
reviewing their existing tests as part of their work, and
ask them to set in this field one of the following 4
values:
1. READY – if the test is OK and it can be run as is.
2. TO REVIEW – if you think something can be update in the test to
make it better. In this case you may also want to add a comment with
why you set it to it.
3. TO REPAIR – when there is something that needs to be changed. In
this case too, write down what you think should be fixed.
4. OBSOLETE – when the test should simply be discarded.
By having these fields you will be able to review them a lot easier. You will
also be able to see what tests are “abandoned”, by looking for tests that
after a couple of cycles still have no value filled on this field. Abandoned
tests are usually useless and should also be discarded.

3. The last step is the trivial one.
You need to set time aside to clean your
tests.
The best time (and often enough the only
time) you will have is in the short span
between projects.
If you plan this ahead and make sure that no
one else has already assigned a task for you
and your team, you may be able to review all
your tests. In case you are not able to go
over all of them at least start from the most
critical areas of your product.
Make it a habit for
your testers to
work correctly
Ask your testers not to
write unneeded tests,
and to always place tests
in their correct place
within the test tree.
Step3: Set time aside in your schedule
before your next “big project”
Keep touch, tweet or share
For more helpful insights, tips for testers and more visit
our blog: http://qablog.practitest.com