While the word “test” may dredge up painful memories of suffering through high school or college examinations, testing serves an essential function in the Clarity upgrade process.
If you’ve spent any time in software development, you’ve no doubt heard the terms “regression testing” and “user acceptance testing” (UAT). But how are they different? And when do you use each one?
Let’s break it down.
What is Regression Testing?
Regression testing is a software testing practice that ensures an application still functions as expected after any code changes, updates, or improvements.
Changes in the code may involve dependencies, defects, or malfunctions. Regression testing mitigates these risks, so the previously developed and tested code remains operational after new changes.
What is User Acceptance Testing?
In contrast, UAT is when actual users test the software to see if it can perform the required tasks in real-world situations. It’s important to note that UAT must adhere to customers’ requirements. UAT testers aim to validate changes made against original specifications and are usually the last test cycle before the Production release.
When Should I Perform Regression Testing?
Regression testing occurs after any change to the code base. It should also be executed when a previously discovered issue has been marked as fixed and must be verified.
Version Upgrades to an Application are a prime example of an activity requiring Regression Testing.
Basic Clarity Regression Testing: Define Test Cases/Scripts to Execute
The following list will help you get started with regression testing in Clarity.
- User Interface:
- Compare the Navigation and Layouts to current configuration.
- Validate the Edit Capabilities of several Key Attributes.
- Interfaces/Data Feeds:
- Review Inputs and Outputs.
- Views (Portlets/Key Reports):
- Execute everything
- Scheduler connections:
- MSP, Open Workbench, Gantt, etc.
- Create at least one of the following:
- Project, Resource, Idea, Custom Investments, etc.
- Check that jobs are running successfully, and ensure processes executed from jobs are completing without error.
- Workflow Processes:
- Run through all Active User and System Initiated processes.
- On Premise:
- Validate any customizations against your environment.
Advanced Regression Testing
- Review the list of resolved defects and new features delivered within releases for potential impacts to your use of the tool, including testing relevant scenarios.
The upgrade’s release documents should be reviewed for business impact. These documents are accessible from Broadcom’s TechDocs site.
- Review Release Notes, which outline new features, enhancements to existing features, resolved issues, known issues, and third-party software agreements.
- Examine the Change Impact and Upgrade documents. These help you learn about the changes, identify their impacts, and discover the required actions for your upgrade.
- Test and prepare training for any new Clarity features you plan on leveraging immediately upon upgrade deployment.
- Performance testing:
- Execute random testing comparing to current timings for things like timesheet processing, resource planning views (use OBSs selection options), scheduler connection, and screen refreshes.
- Place emphasis on activities that impact users daily use and timeliness and accuracy of reporting.
- If users employ multiple browsers, perform testing in all accepted browsers.
Let Rego Guide Your Upgrade Journey
Are you facing resource issues when it comes to finding teams to perform release updates? Rego specializes in delivering world-class upgrades for Clarity–we average one upgrade every three days. Our expert consultants will give you the end-to-end support you need to drive project momentum and successful end-user adoption. Contact us today to get started.
Rego offers free configuration and adoption assessments, webinars, and half-day training classes for Clarity PPM on Roadmaps in the Modern UX, Power BI, Portfolio Management, and Jaspersoft.
For a full list of Clarity PPM services, visit regoconsulting.com.