Article

Execute E2E Testing

While the Scrum team is conducting unit testing on specific units of code, there should be a broader quality assurance process. Imbedding continuous testing as part of your process and testing early and often are good practices to identify issues as close to the development cycle as possible, where fixing them is much easier. As part of the project’s quality planning, the team should decide what kinds of testing will be executed and when, as well as identify the appropriate resource types and resource levels needed to support the quality plan.

 

What

Continuous testing includes end-to-end testing, which tests functionality of the screens with the accuracy of the data in each field. End users must also be engaged to conduct their own scripted or unscripted testing to become familiar with the new application and raise any issues, as they are the most familiar with the process and can also provide useful feedback on the usability and accessibility of the new application. Performance testing is also conducted, usually by a separate dedicated team, based on performance test plans. These tests are designed to measure the performance and speed of the application - how fast the screens and data refreshes. They may have specific Service Level Agreements (SLA’s) which will need to be tested.

Lastly, some customers may engage third parties to conduct penetration testing, aimed at making sure customer data is protected and accessible only to approved users.

Why

Testing is used to validate the working software against what was planned to be built. Without an effective test process, it would be difficult to measure whether the application meets the requirements and functions as designed. Testing includes functionality as well as data accuracy, data security and system performance. Traditional test processes requires the gathering and prioritization of documentation that defines the working software. This can be a lengthy process and very limited to adaptability to changes in design or priorities.

 

With Pega, we accelerate documentation and adaptability to change by the use of Direct Capture of Objectives (DCO), the case type backlog tool and rapid prototyping. We accelerate software development by the use of PegaExpress, Rules, and Applications. Testing in Pega should still go through the classic phases of Unit Testing, System testing, User Acceptance testing and Performance testing. The difference is how we perform those test phases.

 

How

Planning for continuous testing is an integral part of the project management process. There are specific tests with their respective testing objectives, which should be defined, planned and executed throughout the project. Testing should be incorporated in every Sprint and not deferred until the end of the project, where it may be too late or too costly to remediate defects or misalignments with requirements and acceptance criteria. As part of Sprint Planning, tests to be executed and who will execute them outside the Scrum team should be discussed and planned, so they become part of the Definition of Done for each Product Backlog item.

 

Published May 8, 2018 — Updated January 11, 2019


100% found this useful

Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.