Skip to main content
Skip table of contents

Sprint Testing and release Guidelines.

  1. Mandatory Impact Area Field

           The Impact Area field in JIRA will be mandatory for all bugs when transitioning to the In Review status. This ensures that developers (DEVs) review and capture the impact on the ticket. QA can collaborate with DEVs if additional clarity is required.
This field will be enabled in WEMAIN project, and all teams will be informed to follow for their Bugs.

  1. Extensive Use of MABL

  • QA will extensively use MABL during the sprint to test tickets. Affected modules and client cases will be tested as soon as all bugs related to them are resolved, rather than waiting until the final hours of the release.

  • Suites can be re-run if any ad hoc changes arise, as setting up the suite initially streamlines subsequent runs.

  1. Review of Automation Test Cases

           QA, with the assistance of the Product Owner (PO), will review test cases intended for automation to ensure alignment with the release objectives.

  1. Automation Before Deployment – Track with a JIRA Task in every release

           The PO will ensure that automation is executed for all modules and clients included in the release before marking it ready for deployment. The expectation & results to be captured in a JIRA Task, in every release.
Expectation:

PO will create a Jira ticket at the start of the sprint considering the Areas of impacts in the sprint items. QA will create and execute the Mable suite accordingly.
PO will release the version only after this ticket is marked DONE.
Owners: PO and QA.

  1. Post-Release Automation

           QA may run automation for clients without direct release impacts, either before or after the release, if deemed necessary based on bug analysis. This helps maintain a QA-certified build ready for upgrades.

  1. Client Upgrade Intimation

           The PO should be informed before any client upgrade to ensure automation is executed. The Services/CSMs team must notify the PO accordingly.

  1. Ad Hoc Releases

           For ad hoc releases, QA will prioritize and select test cases to run based on their judgment, remaining time, and impact areas. Test runs will be triggered in parallel with manual testing. As we progress, we will refine this process.

  1. Any deviations or necessary amendments to the above plan should be reported to Managers and discussed during sprint retrospectives.

  2. QA should make sure adding the Issue Category, Test Case Linked, QA assignee and QA estimates before closing any ticket.

  3. QA should create QA tasks for the tasks out of sprint like regression testing, Automation support and Product KT.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.