Testing is the roadmap to quality. While running now small iterations (for example 2 weeks). I will tell you, in a 2 weeks sprint you don't have 3 weeks' time for testing. And you don't want decrease in quality testing... you want, you must invest in test automation. Testing should start asap after start the sprint. Test Driven Development can help you fast forward (in time and quality)
Test-automation will help you to automate lot of below mentioned processes.
your company wants to be sure:
The software, middle ware and hardware in production is reliable.
The software exactly has the kind of quality the customer wants.
To reach that quality in production you have to make your development process:
To do list Testing:
With static testing the end products are assessed without software being run. This test usually consist of the inspection of documentation. If you let all the documentation of a software development project be reviewed by a group of people with different knowledge, functions and focus areas you will find defects in an early stage.
At least one test or (chain) analyst should be involved in every review.
Monitoring test findings after going live
There is an important given in the test world; “There is a big chance that the defects you find during the first 3 months after you go live, are missed defects during your last test period.” This means your test coverage was (probably) not good enough. We can learn from our missed defects and improve our test process in an easy way.
Determine for every incident not only the solution for this incident, but also for future incidents by:
Every team needs several D or T environments
Every team needs stubs and drivers (for testing the interfaces in an early stage)
Every team needs one T environment with connections (for testing interfaces)
Virtualize D and T environments (automatically deployment environments, automatically deployment connected-T)
Improve connected-T environment and arrange maintenance
The connected T-environment will and must grow and change during the project and change scheduler of the company
Introduce a test counter for requests for test environments, test data, test support (technical)
Availability of an end to end test environment is mandatory (just like the End to End test if you change something in the End to End process).
Definition: A regression test is designed to verify that all the unchanged parts of a system still function correctly after the implementation of a change.
A regression test is designed to verify that all parts of a system still function correctly after the implementation of a change. In approximately 30% of the cases that you change an application, a new mistake is introduced or an old one is being activated. This can be a mistake in a completely different area of the system than the part where the original fault has been rectified. That’s why testing the whole system by means of a Regression test after the changes have been implemented is so important
Monitor coverage of requirements in a Traceability matrix
A traceability matrix is a type of document that helps correlate and trace business, applications, security or any other requirements to their implementation, testing or completion. It evaluates and relates between different system components and provides the status of project requirements in terms of their level of completion.
At the end the stakeholders can trace the whole life cycle of the requirement from start till end and have all the results available.
TMAP Next Definition
The test policy describes how an organisation deals with the people, resources and methods involved with the test process in the various situations.
If you want a predictable quality of your software, you need a test approach that is proven before. To be sure that all project teams and DevOps teams will deliver the same quality of software at the end (also in the future), you must arrange it in such a way that the way of working and the test approach is available for everyone and embedded in the change organisation.
To be sure that everyone knows which test approach your company uses and to make all the tools available, and write the Test Policy.
It applies to all types of systems, infrastructures and development methods. It is recommended to connect the different policies of the organization. We identify the following subdivision:
Copyright @ All Rights Reserved