Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

The article provides a description of the role of a Quality Assurance (QA) analyst in software testing projects. The main responsibilities of a QA analyst include conducting functional testing and regression testing before the customer performs their testing. The article also mentions additional tasks that may be fulfilled based on project needs and QA allocation, such as helping the customer with User Acceptance Testing (UAT), test management, functional demos, and test automation.

QA Role Description

Let’s escribes the standard role of a Quality Assurance (QA) analyst in software testing projects. The main responsibility of a QA analyst is to conduct functional testing before the customer performs their own testing. Functional testing involves evaluating the software's functionality to ensure that it meets the specified requirements. Additionally, the QA analyst assists the customer with testing tasks during Feature Sprints and User Acceptance Testing (UAT).

  • In this context:

  • "Functional testing" refers to the process of testing the software's functionality to ensure that it works as intended.

  • "Feature Sprints" typically refer to short development cycles focused on implementing specific features or functionalities within the software.

  • "User Acceptance Testing (UAT)" is a phase of software testing where the software is tested in a real-world environment by the end-users to ensure that it meets their requirements.

QA tasks and responsibilities

Here are main tasks QA analyst should fulfil:

Other tasks can be fulfilled in case of project needs and sufficient QA allocation:

  • Helping customer with UAT (tips for less experienced customers)

  • Helping customer with test management especially when customer has no own test management tool

  • Functional demos for customer

  • Basic performance testing (optional, expected for large project, support from Performance team can be needed for complex scenarios)

  • Test automation for supporting development (optional, based on allocation and project needs)

  • Review of Acceptance Criteria in case QA allocation is from Foundation sprint

  • No labels