Pages

Sunday, May 2, 2021

Templates for JIRA

Fill required details in place of <> in the template

Filing JIRA

Use the below template while filing JIRA:

Lab info

Lab:

<Server name> e.g., NA productions

Loads:

<Server load> eg., CPaaS 2.1.4

<Browser with version> e.g., Chrome Version 72.0.3626.121(64-bit)

Timestamp:

<Date and time in EST> e.g., March 17, 2019 8:10-8:25 PM EDT

Setup:

e.g.,

URL: https://project.company.com/

Account: test@ask-mail.com

Password: Test@123

Steps:

<Mention all the steps in number bullet points>

Actual Result:

<>

Expected result:

<>

Reproducible:

<Yes/No with comment> e.g., Yes, but with trial accounts only

End User Impact:

<Adequately assess the impact of this issue on end-user> e.g., It would heavily impact the performance of call under specified scenario

Frequency:

<occurance rate> say., 100%

Fault Isolation:

<If you know which module the fault is> otherwise say., None


Validating JIRAs

Steps to verify:

Login to server <Staging URL/Production URL> with account <email id/password>

<1. ...

... n.>

Narrate the clear steps to verify the JIRA

Expected results:

<> write clear notes on what should be the expected results aligning with Jira requirement. If you are not sure of the req, bring it to the discussion on JIRA itself.

Actual results:

<> say., works as expected, if not mention the actual result observed.

Date/Time of test:

<> Eg., March 26, 2019 10:30 AM EST.

Conclusion:

<PASS/ FAIL>

Next,

Move the JIRA to “ TESTING DONE ” status if the test is a pass, Assign Jira to Project Admin.

If the test fails, keep the JIRA in ‘TESTING’ state and assign to Project Admin clarifying the requirement, Jeff may want to correct steps or take further action in redoing development changes. Repeat testing if required.

No comments:

Post a Comment