Comparison of Change Management Systems

48
Software Testing
motivating if the tool is user friendly.
Unfortunately it is rarely the first reason!
2.2 Eight Low level concrete reasons…
(More valuable)
2.2.1 A good cooperation between the
stakeholders
Business Owner, IT Project manager,
Test Manager, Testers, Suppliers and
other external partners use the Test
Management tool in different ways.
A Business Owner is expecting Proofs of
testing and a status of the Requirements
implementation...
An IT Project manager has to get
information from the bottom and provide
information to the top.
A Test Manager has to manage the
testing activities quickly, get and provide
information to the Project manager and
check outsourced testing activities.
Testers need to know what to do while
tests execution.
Suppliers and Other External Partners
have to build their tests from the right
requirements and provide visibility on
their testing activities.
2.2.2 Centralization (tests, tests
executions and results)
Everything is at the same place, no more
files to look after, and no more versions
to fight with. Isn’t it a good reason?
2.2.3 Easier reporting at several levels
(Document generation)
Depending on your needs and your
position, the tool should be able to easily
generate the reports you need to make a
decision or give an approval.
Testers need to know what they still have
to do.
Tests manager must be able to quickly
answer the following questions: What
are the remaining testing tasks? What is
the real status of the tested components,
applications or system?
A project manager needs the answer to the
following questions: How is testing going
on? Where are the main weaknesses in
the tested items? What is going wrong in
Picture 1 A good cooperation between the stakeholders
Picture 2 Efficient and Real-time reporting at several levels (single repository)