Automation Testing Suite

The IT industry is moving rapidly toward "shift left" and at DCS we aim to build world-class test harness that helps our clients, co-vendors to speed up their testing. the "shift left" testing movement is about pushing testing toward the early stages of software development. By testing early and often, a project can reduce the number of bugs and increase the quality of the code.

DCS Automation Testing Suite provides a Selenium-based test framework to build up a test automation suite for your Pega application. With this test framework, you can validate both UI-based scenarios and headless APIs. This can be plugged into Pega Deployment Manager or any other widely used CI/CD DevOps tools like Jenkins.

Our test component starter kit comes with a generic Selenium-based framework that clients can adopt for creating UI page objects and tests for their Pega applications. It also includes the REST components to validate both SOAP and REST APIs. Our UI test framework supports testing core Pega intelligent automation, Pega Customer ServiceTM, and Pega Customer Decision HubTM. The kit comes with out-of-the-box sample tests to validate real core use cases of those CRM applications. The framework and tests are based in behavior-driven development and use the Cucumber framework.

• System testing/regression pack that is automatically triggered by integration builds
• UI and API automation framework, which is a combination of Selenium, Rest Assured, Cucumber, TestNg, and Java
• UI scenarios that are written in Gherkin language in feature files
• TestNg xml file that has reference to the runner class, invoking features based on tags
• Code management using GitHub
• Fully automated testing framework selected by the DCS-ST team
• Pega Deployment Manager as the build management tool for the CI/CD pipeline
• Running testing tasks through automation is 60-70% faster than the manual testing
• More cycle of execution can be achieved through automation
• Early time to market
• Reliable in results (as human intervention is not required while executing)
• Wider test coverage of application features
• Ensured consistency
• Time and cost savings
• Increased efficiency/productivity
• Better speed in executing tests
• Reusable test scripts
• Frequent and thorough testing