Testing during project life cycle

Testing during project life cycle:
The Tenure of the project and the number of Roll-outs forms the criterions whether the project life cycle testing should be automated or not. If the automated scipts already exists, the same may be fine tuned for the said projects/Roll-outs.
For the new projects and Rollout the following testing cycle can be automated:

Project-Unit testing:
This can be intitally manual during the build/development cycle but subsequently can be automated.It will aid in saving time and effort if changes and new requirements are introduced during project execution cycle. At this stage, both individual and combined test scripts can be used for the SAP transactions that form unit testing cycle. If the automated scripts already exists, the owner of the automated testing scripts can provide already validated scripts for the current and future projects.

Project integration Testing:
Automated testing can be helpful in integration testing cycle for projects. However, the initial integration tests should be performed and validated manually and later on switched over to automated testing. Impact of bugfixes or the changes can be tested efficiently and quick turnaround would be possible to meet the project milestones.

Project-User acceptence testing:
User acceptence should also be done manually first and than subsequently automated to be used for tests as and when the need arises. It would bring value if the same soultion is to be rolled out to mutiple locations. After the project Go-Live, user accepetence test scripts can be used by the support team for ongoing change management and Regression testing.

Comments

Popular posts from this blog

2.Areas of Deployment

Setting Actions as Reusable Actions

Sample QA/Testing Resume