Primary Responsibilities: –
- Learn and gain in-depth knowledge of various software products and testing methodologies of the organization
- Get involved in analyzing requirements (epics and stories) during the requirements analysis phase of projects
- Identify the gaps and clarifications in requirements, bring it to the notice of Lead, Product Owner and ensure to track the findings to closure
- Keep track of any new requirements / changes during the process of requirements understanding and clarification process
- Document, implement, monitor, and enforce all processes and procedures for testing the product / project are established as per standards defined
- Write detailed test cases to ensure optimal test coverage of software product features; Prepare traceability matrix to validate the test coverage
- Understand product specification and verify if product behaves as expected across releases in multiple environments
- Review the test deliverables produced by other team members and enter the review findings in the defect management tool identified for the project
- Methodically document steps which exhibit a problem and can reproduce and communicate these steps
- Track and report upon testing activities, including testing results, test case coverage, required resources, defects discovered and their status, etc.,
- Ability to analyze a specific problem reported, identify the root cause and generate a detailed report
- Interact with team leader on project status and resolution of critical issues; Promptly escalate unresolved dependencies and issues.
Key Activities: –
- Analytically driven: comfortable with critically analyzing stories and functionality
- Self-sufficient: capable of independently creating the test cases, test scenarios and executing them
- Personal accountable: capable of doing sufficient self-review of test cases
- Quality focused: capable of testing enough to ensure quality
- Develops team: comfortable and willing to do test case reviews. Identifying effective functional gaps in test cases
- Effective communicator: capable of clearly articulating bugs, blockers, ideas or requirement clarifications. Writes and speaks clearly expressing their thoughts and ideas
- Strong Team Player: Finding bugs in developer’s code and clearly expressing it while still maintaining a positive relationship with developers. Consistently embracing a communication style that does not make developers feel blamed
skills Must
- Good analytical skills and self initiative to learn new testing methodologies and techniques
- Ability to work as part of a global team with good communication skills (written and spoken English)