Manual QA lifecycle

Job Description:

Mandatory skills: Manual QA lifecycle: Strong foundation in all aspects of the lifecycle including QA artifacts. •Domain Experience: understand the terminology, concepts, and process flow for a Insurance claim and policy. •Excellent analytical skills to identify defects and ensure comprehensive test coverage. •Technical: Working knowledge of SQL Select statements, Postman, Guidewire integration gateway Desired Skills: Application experience: Guidewire PolicyCenter and ClaimCenter. •Domain Experience: understand the terminology, concepts, and process flow for an Insurance billing system and integration with policy and claim systems. •Technical: proficiency with qTest, Jira, Guidewire integration gateway •Azure technical: Testing within an Azure cloud infrastructure. Additional skills: Azure Functions, API Management (APIM), and Azure SQL/NoSql.

•QA lifecycle: Independently manage and execute the manual Test Management process. Draft QA artifacts: test plans, test scenarios, test cases, requirements traceability, and test execution results.
•Testing Types: draft execute test cases for functional, regression, integration, and end-to-end testing for user interfaces and APIs. Facilitate the user acceptance test.
•Requirement analysis: analyst requirements in the form of user stories and design review meetings
•Defect management. Identify, document, and track software defects in Jira. Collaborate with developers and business analysts to resolve defects retest resolutions, and improve software quality.
•Agile or Azure DevOps Methodology: Collaborate with developers and business / technical analysts using an agile and DevOps approach to deliver QA artifacts.
•QA Risks: Identify, communicate and manage QA risks to proactively avoid issues preventing completion of QA artifacts
•QA metrics: track and collect data that enable insight into the effectiveness and efficiency of the QA lifecycle.
•Regression test suite: Create, maintain, and execute a regression test suite to ensure application changes do not negatively impact existing functionality.
•Communication: provide stakeholders with timely information on QA execution via email, daily stand-up meetings, and reports