1 Upgrade Definition
2 Testing Performed by Krishagni
3 Customer Testing Best Practices
- 3.1 Release notes
- 3.2 Testing approach
- 3.3 Test Plan
- 3.4 Testing Collection Protocols (CPs)
- 3.5 Maintaining Test Execution Logs

Upgrade Definition

There are two types of upgrades:

Upgrade Type

Frequency

Contains

Version Upgrade

E.g., v10.1, v10.2

Once per 3-4 months

New features, bug fixes, security fixes, ease-of-use (UX) enhancements, performance tuning, etc.

Patch Upgrade

E.g., v11.1.RC1, v11.1.RC2

Need based

Fixes for critical bugs or security issues.

No new features added in the patch release.

Testing Performed by Krishagni

Krishagni conducts the following levels of testing for every release:

Upgrade Type	Testing Performed
Version Upgrades	Regression testing (testing to ensure old features are not broken) Unit & functional testing for bug fixes and new features Performance testing
Patch Upgrades	Smoke testing of all features Unit testing for specific bug fixes only

Customer Testing Best Practices

Release notes

Krishagni publishes release notes for every version. Read the release notes for each version to understand “what’s new” in each release to determine your testing strategy. For example, if you are upgrading from v10.2 to v11.2, you must refer to the release notes for v10.3, v11.1, and v11.2.

Testing approach

Upgrade Type	Project Team / Admins	End Users
Version Upgrades	Verify bugs and enhancements of interest Validate new enhancements impacting workflows	UAT: Smoke testing with scripts mimicking ‘day-in-the-life’.
Patch Upgrades	Confirm resolution of targeted bug(s)	Minimal or no testing unless the bug directly affects them

Test Plan

Customers should create a Test Plan based on their day-to-day use of the application. It should cover the following:

Typical data entry workflows
Most used features
Should be updated regularly based on new features used, new groups onboarded, process changes, etc.

Testing Collection Protocols (CPs)

It would be easier if you created some CPs dedicated to testing, which have all the configurations and workflows pre-configured. Ensure that no user edits these protocols.

Maintaining Test Execution Logs

For regulatory and compliance purposes (e.g., CAP certification), you should maintain a formal “Test Execution Log” per release, which contains details like:

Tested by
Dates
Execution results per test case

How to test OpenSpecimen after upgrade?