QA Flashcards

(36 cards)

1
Q

Quality Assurance (QA)

A

The process of ensuring software meets required standards before release.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Defect / Bug

A

An error, flaw, or problem in the software.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Requirement

A

A specific condition or capability that the system must satisfy.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Test Case

A

A set of conditions to verify a feature works correctly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Test Plan

A

A document describing testing scope, approach, and objectives.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

User Story

A

A short description of a feature from the end-user’s perspective.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Acceptance Criteria

A

The conditions a feature must meet to be accepted.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Severity

A

The impact of a bug on the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Priority

A

The order in which bugs should be fixed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Environment

A

The setup where the software is tested (e.g., dev, staging, production).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Requirement

A

A condition or capability the system must meet.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Specification (specs)

A

A detailed description of system design or functionality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Functional Requirement

A

Defines what the system should do (features, actions).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Non-functional Requirement

A

Defines system qualities (performance, usability, security).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Ambiguity

A

Unclear or open to multiple interpretations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Edge Case

A

A rare or extreme condition in input or behavior.

17
Q

Scope

A

The boundaries of what will and won’t be included in testing.

18
Q

Dependency

19
Q

Precondition

A

A condition that must be true before executing a test case.

20
Q

Test Step

A

A single action performed during the test.

21
Q

Expected Result

A

The correct outcome after performing the steps.

22
Q

Actual Result

A

What really happens when the steps are executed.

23
Q

Test Data

A

Input values used in a test.

24
Q

Test Suite

A

A collection of related test cases.

25
Regression Testing
Re-running tests to confirm changes haven’t broken existing functionality.
26
Pass/Fail
The outcome of the test.
27
Negative Testing
Testing invalid or unexpected input.
28
Issue ID / Ticket ID
Unique number assigned to a bug in a tracking system.
29
Steps to Reproduce (STR)
Exact steps to make the bug appear again.
30
Severity
How badly the bug affects functionality.
31
Priority
How urgently the bug should be fixed.
32
Expected Result
What should happen according to requirements.
33
Environment
The setup where the bug occurs (staging, production, browser, OS).
34
Reproducibility
How often the bug occurs (always, sometimes, rare).
35
Attachment / Screenshot / Log
Supporting evidence included in bug reports
36
Defect Lifecycle
The stages of a bug (new, assigned, fixed, verified, closed).