Video Notes: QA Role in Agile - Vocabulary Flashcards

Vocabulary flashcards covering key concepts from the 'QA Role in Agile' video notes.

QA role in Agile

The set of QA responsibilities in an Agile environment, including document review, meetings participation, defect reproduction, test planning, automation, and collaboration with PO, PM, BA, DEV, and SME to ensure product quality.

Continuous study of project documentation

Ongoing review and upkeep of all project documents to stay aligned with requirements, acceptance criteria, and evolving scope.

Attend Scrum/Project Meetings

Participating in project and Scrum ceremonies to keep the QA team informed and aligned with status, risks, and upcoming work.

Capture complex and negative behaviors in AUT

Identify and document non-happy-path issues and complex defects in the Application Under Test (AUT).

Happy path

The ideal, expected flow where the system behaves correctly; QA also tests edge cases beyond this path.

Test Case (TC)

A documented set of inputs, steps, and expected results used to verify a specific function or requirement.

Test Scenario (TS)

A high-level description of a feature’s behavior used to guide creation of test cases.

Clarify questions with stakeholders

Ask Product Owner (PO), Project Manager (PM), Business Analyst (BA), Developers (DEV), and SME to resolve requirements and ambiguities.

Pairing with developers

Work with developers to reproduce defects, discuss QA test scenarios, and share testing insights.

Reproducing defects

Process of reproducing a reported defect to confirm its existence and observe the failure.

Unit Test Cases

Tests that verify the behavior of individual units or components in isolation.

Regression Testing

Re-running existing tests after changes to ensure new code changes didn’t break existing functionality.

Regression Test Suites

A collection of regression tests grouped to be executed together.

Negative Testing

Testing how the system handles invalid inputs, errors, or unexpected conditions.

Boundary Testing

Testing at the edge of input ranges to verify boundary behavior.

Smoke Testing

A quick set of tests to verify that the major functions work after a build.

Ad-Hoc Testing

Informal, exploratory testing performed without formal scripts to discover issues quickly.

Retesting

Re-executing tests after defect fixes to confirm resolution.

Defect fixes

Code changes implemented to resolve defects found during testing.

DoD (Definition of Done)

A set of criteria that must be satisfied for a product backlog item to be considered complete.

Test Deliverables

QA outputs such as Test Strategy, Test Plan, RTM, Test Cases, and meeting Minutes.

AUT (Application Under Test)

The software product or component being tested.

RTM (Requirements Traceability Matrix)

A matrix mapping requirements to test cases to ensure coverage and traceability.

Minutes

Notes taken during QA/project meetings detailing decisions and action items.