Skip to content
Gallery
Software Quality Assurance Engineer
Overview
Software Quality Assurance Engineer
Learning
Products
Share
Explore
Software Quality Assurance Engineer

icon picker
[For Review]My Day to Day

Check Emails

Emails provide notifications on activities, ensuring you stay updated on important events and communications.
Emails often include meeting invites that need to be accepted or declined promptly.
Regularly checking emails is crucial for staying informed and maintaining effective communication in the workplace.
Organize your inbox by categorizing and prioritizing emails to enhance productivity.
Set specific times to check and respond to emails to manage your time efficiently.

Check Jira Board
Regularly check your Jira board to stay informed about your assigned tasks and responsibilities for the day.
Always update your Jira tickets to keep your team informed about the current status and progress of your tasks.
Your superiors and peers rely on the Jira board to monitor your progress, velocity, and overall team performance.
Break down tasks into smaller sub-tasks within Jira to manage and track progress more effectively.
Utilize Jira comments and attachments to provide detailed updates and collaborate with team members.
Update status of ongoing tasks
Review and prioritize new tasks

Attend daily stand-up meeting
Share testing progress and blockers
Note development updates and timeline changes

Execute test cases
Follow test plan and prioritize critical areas
Document test results (pass/fail, test data, screenshots, video demos)
Log defects in the bug tracking system
Provide clear descriptions, steps to reproduce, and evidence

Collaborate with developers
Discuss defects and clarify issues
Understand root causes and potential fixes

Attend project meetings or discussions
Share testing updates and concerns
Discuss testing strategies and approaches

Review requirement changes
Update test plans and test cases accordingly
Identify impact on testing scope and effort

Perform regression testing
Test previously working features after changes
Verify no new issues introduced
QUESTION: When to do Regression testing Tito Ram?? After major version release of an app??

Verify and validate defect fixes
Test fixed defects in the latest build
Confirm fixes and close defects

Conduct exploratory testing
Identify potential issues or edge cases
Document findings and create new test cases

Analyze test results
Identify patterns, trends, or areas needing more testing

Update test metrics and reports
Track testing progress, defect trends, quality status (Google Sheets)

Participate in code reviews
Provide QA perspective
Identify potential issues early

Throughout the day, additional activities may include:
Developing and maintaining test automation scripts
Conducting performance, security, or usability testing
Providing training or mentoring to junior QA team members
Researching and evaluating new testing tools or techniques
Update task lists, test plans, and defect tracking systems
Communicate critical issues, risks, or concerns
Prepare for next day's testing activities
Attend team retrospective meetings (if scheduled)
Discuss lessons learned and process improvements

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.