Suggestions
Shri Rachana Rajasekaran
Software QA Engineer - 2 at Intuitive, ex-Amazon
Shri Rachana Rajasekaran, Software QA Engineer - 2 at Intuitive
Shri Rachana Rajasekaran is a Software QA Engineer - 2 at Intuitive, a medical device company that develops robotic-assisted surgical systems.1 She has over 500+ connections on LinkedIn and is based in San Jose.1
Some key points about Shri Rachana Rajasekaran:
-
She has shared posts on LinkedIn discussing topics related to software quality assurance, such as the definition of done from a QA perspective2 and general quality-related topics.3
-
She attended SHRI RACHANA DEVELOPERS CENTER CREATION B.S.W. COLLEGE RAJKOT, a higher education institution in Rajkot, Gujarat, India.456
-
Her LinkedIn profile showcases her experience in software engineering, quality assurance, and agile methodologies.7
-
She is part of a community of software quality assurance professionals on LinkedIn, with connections to other QA engineers like Shirni Arekapudi from Meta and Aiona H. from Instructure.78
Highlights
✨Test Plan for the ages✨ Keep it simple and ensure all the relevant details are captured ✨Test Plan Template ✨
💡 Introduction 💡 Purpose
- Purpose to outline the test approach, pass/fail criteria, and deliverables for the project. -The scope is provided in the milestone. 💡 High Level Requirement : -Call out the individual requirements for the release. 💡 Definitions -Define your test systems example - BAT/Smoke test, load testing, KPI, P0 through P3 💡 Test Strategy 💡 Scope -List out "In-Scope" areas -List out "Out of scope" areas 💡 Test Cases 💡 Test Dependencies 💡 Hardware 💡 Software 💡 Defect Management -List the jira labels 💡 Traceability 💡 Schedule 💡 Risk Analysis and Open Questions -List "Risk-Impact-Impact analysis" 💡 10)Approvals for sign-offs 💡 11)Validation Documents for routing 💡 12)Supporting Doc and Agile Numbers
Here are some additional tips for writing a good test plan: ✅Be clear and concise. The test plan should be easy to understand by everyone involved in the testing effort. ✅Be specific. The test cases should be specific enough to ensure that the software is thoroughly tested. ✅Be realistic. The test plan should be realistic in terms of the time and resources available. ✅Be flexible. The test plan should be flexible enough to accommodate changes to the requirements or the software.
By following these tips, you can write a test plan that will help you ensure the quality of your software. #qa #quality
✨Better Bug report means lesser regressions ✨ As a QA, you know that bugs can be time-consuming to reproduce and explain to developers. Over time, you learn to write efficient bug reports that help you achieve the following outcomes: ✅ Reduce time spent with developers explaining the bug. ✅ Avoid future regressions. ✅ Understand the impact of the bug. ✅ Improve product quality.
✨Bug Report Template ✨
1)Bug Title : A brief, descriptive title that summarizes the bug. [Project_Title][Sprint_Number][P0][Title]
2)Steps to Reproduce : Detailed instructions on how to reproduce the bug.
3)Expected Results : Link to PRD/Figma if available Based on Test Case that satisfies Spec/ PRD
4)Actual Results : Actual behavior of the system while following the 'steps to reproduce'
5)Reproducibility : How often the bug can be reproduced. QA :X/5 UAT : X/5 Prod : X/5
6)Severity/Priority : P0/P1/P2 (Provide resolution SLA and link the wiki as needed)
7)Build Details : Device Details Build Number and Jenkins link User Login details (If available)
8)Attachments : Log file [Example : adb logcat] Screenshot Audio/Video grabs
9)Jira Tags/Tool Tags : Tags that can be used to categorize the bug and track its progress. Tag the report with the right tags so it shows up in the correct dashboard
10)Resolution : A proposed resolution timeline for the bug. Provide a fix date (Dev Task typically, however suggestions from the QA are critical)
#qa #quality
