Gallery

QA Training Syllabus

Mobile Testing

Web Testing

Flutterflow automation

Performance testing

Explore

Regression Process

Set a timeline first

Prepare your test cases, make sure your test cases is updated with all the new features and present features

Ask your project manager for the proper timeline, and heads up before starting your regression

Get the testing environment from the developers or project manager

WEB - Clarify from the team if the provided link is staging or production environment

MOBILE - ask for apk staging to test on android or mobile simulator (e.g, browserstack, bluestack) AND for iOS if the application is deployed on testflight

Reminders:

Inform your pm that there should be no deployment during regression week

always use the staging or dev environment

For test cases, update the status (No Started, Passed, Failed, Blocker, Deferred)

For JIRA Bug Template

[MODULE] Bug title

Details:

Environment: Staging

App version:

Build no.:

[Mobile] Device Used: Redmi Note 10 Pro

[Mobile] Operating System: Android

[Web] Browser: N/A

Issues:

User are unable to login due to error displaying the message: “Oops! User not found.”

Expected Result/s:

User should be able to login.

Steps to Replicate:

Open SIT app

Test Evidence:

*insert recording or screenshots*

Linear Bug Template

You can click this for automatically creating bug template

⁠

Now, complete the fields

[Insert Ticket Title]

Details:

Environment:

App version:

Build no.:

[Mobile] Device Used:

[Mobile] Operating System:

[Web] Browser: N/A

Issues:

Expected Result/s:

Preconditions:

Steps to Replicate:

Test Evidence:

For Bug management,

Every end of the day submit bug reports to the team and always cc your PM!

Example:

**REOPENED TICKETS:** -

https://slmc-ehub.atlassian.net/browse/EHUBBUG-213⁠

⁠

bug 2

bug 3

**PARKED & BENCHED:**

bug 1

bug 2

bug 3

**LATEST LOGGED TICKET/S:**

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-218⁠

⁠

bug 2

bug 3

After 2-3 days of regression, all the bugs will undergo bug fixing.

Wait for the bug fixes and retest all the logged bug tickets

Update your team regarding the results of your testing, submit a bug report (like above mentioned)

For Bug Report at the end of the Regression Week

Submit a bug report on the last day of regression week

Bug Summary Example:

Regression Bug Summary

PASSED ON TESTING [n]:

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-187⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-186⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-183⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-182⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-181⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-180⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-185⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-157⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-179⁠

⁠

REOPENED TICKETS [n]:

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-135⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-168⁠

⁠

IN PROGRESS [n]:

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-164⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-131⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-184⁠

⁠

PARKED & BENCHED [n]:

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-151⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-147⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-143⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-91⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-65⁠

⁠

TO DO [n]:

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-163⁠

⁠

https://slmc-ehub.atlassian.net/browse/EHUBBUG-132⁠

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.