Manual QA

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/86

flashcard set

Earn XP

Description and Tags

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

87 Terms

1
New cards

What is Quality Assurance (QA)?

Process-focused activities that ensure quality is built into the development process.

2
New cards

What is Quality Control (QC)?

Product-focused activities that identify defects in the actual product being developed.

3
New cards

What is a Defect/Bug?

A flaw in software that causes incorrect or unexpected results, or prevents it from functioning as specified.

4
New cards

What is the Defect Life Cycle?

The stages a defect goes through: New → Assigned → Open → Fixed → Retest → Verified/Closed (or Reopened if not fixed).

5
New cards

What is Defect Severity?

The degree of impact a defect has on a system's functionality (Critical, High, Medium, Low).

6
New cards

What is Defect Priority?

The urgency with which a defect should be fixed (Immediate, High, Medium, Low).

7
New cards

What is a Blocker Defect?

A critical defect that prevents testing from continuing or blocks major functionality.

8
New cards

What is a Showstopper Defect?

A critical defect that prevents a software release and must be fixed immediately.

9
New cards

What is a Defect Report?

A document describing a defect with details like steps to reproduce, expected/actual results, severity, and screenshots.

10
New cards

What is Defect Triage?

The process of reviewing, prioritizing, and assigning defects to appropriate team members.

11
New cards

What is Root Cause Analysis?

An investigation to identify the underlying reason a defect occurred to prevent similar issues.

12
New cards

What is Retesting?

Testing a specific defect fix to verify the issue has been resolved.

13
New cards

What is Regression Testing?

Re-testing existing functionality after changes to ensure no new defects were introduced.

14
New cards

What is Manual Testing?

Testing performed by humans executing test cases without automation tools or scripts.

15
New cards

What is Unit Testing?

Testing individual components or functions in isolation, typically performed by developers.

16
New cards

What is Integration Testing?

Testing combined modules or components to verify they work together correctly as a group.

17
New cards

What is System Testing?

Testing the complete integrated system to verify it meets specified requirements.

18
New cards

What is User Acceptance Testing (UAT)?

The final testing phase where end-users validate that the system meets business requirements and is ready for production.

19
New cards

What is Smoke Testing?

Quick, shallow testing of critical functionality to verify basic system stability before deeper testing.

20
New cards

What is Sanity Testing?

Narrow, focused testing of specific functionality or bug fixes to verify rational behavior.

21
New cards

What is Functional Testing?

Testing that verifies software functions according to specified requirements.

22
New cards

What is Non-Functional Testing?

Testing of system attributes like performance, security, usability, and reliability.

23
New cards

What is End-to-End Testing?

Testing complete workflows from start to finish to verify the entire application flow works as expected.

24
New cards

What is Positive Testing?

Testing with valid inputs to verify the system behaves as expected.

25
New cards

What is Negative Testing?

Testing with invalid inputs to verify the system handles errors gracefully.

26
New cards

What is Usability Testing?

Testing that evaluates how user-friendly and intuitive the application is for end-users.

27
New cards

What is Compatibility Testing?

Testing to verify software works correctly across different browsers, devices, OS, and configurations.

28
New cards

What is Performance Testing?

Testing that evaluates system speed, responsiveness, and stability under various workloads.

29
New cards

What is a Test Plan?

A document that defines test scope, objectives, resources, schedule, deliverables, and entry/exit criteria.

30
New cards

What is a Test Strategy?

A high-level document defining the testing approach, levels, types, and resources for a project.

31
New cards

What is a Test Case?

A set of conditions, inputs, and expected results designed to verify a specific requirement or functionality.

32
New cards

What is a Test Suite?

A collection of test cases grouped together for execution, typically organized by functionality or test type.

33
New cards

What is a Requirements Traceability Matrix (RTM)?

A document that maps requirements to test cases, ensuring each requirement has corresponding test coverage.

34
New cards

What is a Test Summary Report?

A document summarizing testing activities, results, defect metrics, and quality assessment.

35
New cards

What is Black Box Testing?

Testing without knowledge of internal code structure, focusing on inputs and outputs.

36
New cards

What is White Box Testing?

Testing with knowledge of internal code structure, logic, and implementation.

37
New cards

What is Gray Box Testing?

Testing with partial knowledge of internal structures, combining black and white box approaches.

38
New cards

What is Boundary Value Analysis?

A test design technique that tests values at boundaries (minimum, maximum, just inside, just outside).

39
New cards

What is Equivalence Partitioning?

A test design technique that divides inputs into groups expected to behave similarly, testing one value from each group.

40
New cards

What is Exploratory Testing?

Informal testing where testers actively explore the application without predefined test cases.

41
New cards

What is Ad-hoc Testing?

Unstructured testing without formal test cases, performed randomly to find defects through intuition and experience.

42
New cards

What is SDLC?

Software Development Life Cycle - a structured process framework with defined phases for planning, creating, testing, and deploying software systems.

43
New cards

What are the main SDLC phases?

Requirements, Design, Development/Implementation, Testing, Deployment, and Maintenance.

44
New cards

What is Waterfall Model?

A sequential SDLC model where each phase must be completed before the next phase begins.

45
New cards

What is Agile Methodology?

An iterative SDLC approach with short development cycles (sprints) and continuous feedback.

46
New cards

What is a Sprint?

A fixed time period (usually 1-4 weeks) in Agile where specific work is completed and ready for review.

47
New cards

What is a User Story?

A short, simple description of a feature from an end-user perspective in Agile (As a [user], I want [goal], so that [benefit]).

48
New cards

What are Acceptance Criteria?

Specific conditions that must be met for a feature or user story to be considered complete and accepted.

49
New cards

What is a Stand-up Meeting?

A short daily Agile meeting where team members share progress, plans, and blockers.

50
New cards

What is a Sprint Retrospective?

An Agile meeting where the team reflects on the sprint to identify improvements for future sprints.

51
New cards

What is a Product Backlog?

A prioritized list of features, enhancements, and fixes to be developed in Agile.

52
New cards

What is a Sprint Backlog?

The subset of product backlog items selected for completion during a specific sprint.

53
New cards

What is a Definition of Done (DoD)?

A checklist of criteria that must be met for a user story or task to be considered complete.

54
New cards

What are Entry Criteria?

Conditions that must be met before testing can begin (e.g., test environment ready, test data available).

55
New cards

What are Exit Criteria?

Conditions that must be met to complete testing (e.g., all critical defects resolved, test coverage achieved).

56
New cards

What is a Test Environment?

The hardware, software, network, and data setup where testing is conducted.

57
New cards

What is a Build?

A compiled version of software code that is ready for testing or deployment.

58
New cards

What is a Release?

A version of software made available to users, containing specific features and fixes.

59
New cards

What is Test Execution?

The process of running test cases and comparing actual results with expected results.

60
New cards

What is Test Coverage?

A measure of how much of the application (requirements, code, features) has been tested.

61
New cards

What is Static Testing?

Testing that examines code, requirements, or design documents without executing the software.

62
New cards

What is Dynamic Testing?

Testing that involves executing the software with test inputs and observing behavior.

63
New cards

What is Risk-Based Testing?

A testing approach that prioritizes testing based on the risk and impact of potential failures.

64
New cards

What is Alpha Testing?

Internal testing performed by the development organization before releasing to external users.

65
New cards

What is Beta Testing?

Testing performed by a limited group of external users in a real environment before full release.

66
New cards

What is a Stub?

A temporary replacement for a called module that returns controlled data during integration testing.

67
New cards

What is a Driver?

A temporary module that calls the module being tested during integration testing

68
New cards
My apologies for the misunderstanding. You're right, focusing on the API testing concepts is a smart move as it's a huge part of modern manual QA.

Here are more essential API testing cards in the correct format for importing.

What is an API?
An Application Programming Interface - a set of rules and protocols that allows different software applications to communicate with each other.
69
New cards
What is an Endpoint?
A specific URL where an API can be accessed to perform a particular function.
70
New cards
What is REST?
Representational State Transfer - an architectural style for designing networked applications, often used for creating web services.
71
New cards
What is a Request?
A message sent from a client to a server to ask for data or perform an action.
72
New cards
What is a Response?
A message sent from the server back to the client, containing the requested data and a status code.
73
New cards
What are HTTP Methods?
Verbs that define the action to be performed on a resource (e.g., GET, POST, PUT, DELETE).
74
New cards
What is a GET request?
An HTTP method used to retrieve or fetch data from a server.
75
New cards
What is a POST request?
An HTTP method used to create a new resource on a server.
76
New cards
What is a PUT request?
An HTTP method used to update an existing resource on a server.
77
New cards
What is a DELETE request?
An HTTP method used to remove a resource from a server.
78
New cards
What is a Request Body/Payload?
The data sent to the server with a POST or PUT request, typically in JSON format.
79
New cards
What is a Response Body?
The main content of the response from the server, often containing the requested data in JSON format.
80
New cards
What are HTTP Status Codes?
Three-digit codes returned by a server to indicate the outcome of a request.
81
New cards
What do 2xx Status Codes mean?
Success - The request was successfully received, understood, and accepted (e.g., 200 OK, 201 Created).
82
New cards
What do 4xx Status Codes mean?
Client Error - The request contains bad syntax or cannot be fulfilled (e.g., 404 Not Found, 400 Bad Request).
83
New cards
What do 5xx Status Codes mean?
Server Error - The server failed to fulfill a valid request (e.g., 500 Internal Server Error).
84
New cards
What is JSON?
JavaScript Object Notation - a lightweight, text-based format for data interchange that is easy for humans to read and for machines to parse and generate.
85
New cards
What is Authentication?
The process of verifying the identity of a client to grant them access to an API.
86
New cards
What is an API Key?
A unique code passed in with an API request to identify and authenticate the calling application.
87
New cards
What is Postman?
A popular application used for making HTTP requests to test and interact with APIs