QA

Question 1

[QA] Test Case

Answer 1

A set of conditions or variables under which a tester will determine whether a system under test satisfies requirements.

Question 2

[QA] Test Plan

Answer 2

A document outlining the scope, approach, resources, and schedule of testing activities.

Question 3

[QA] Defect or Bug

Answer 3

Any variance between expected and actual results in the software under test.

Question 4

[QA] Regression Testing

Answer 4

Testing conducted to ensure that a recent code change has not adversely affected existing features. This is usually done before a release.

Question 5

[QA] Black Box Testing

Answer 5

Testing where the tester is not concerned with the internal workings of the system but focuses on the inputs and outputs.

Question 6

[QA] White Box Testing

Answer 6

Testing where the tester has knowledge of the internal workings of the system and can design test cases accordingly.

Question 7

[QA] Smoke Testing

Answer 7

Preliminary testing to reveal simple failures that may lead to rejecting a software build.

Question 8

[QA] User Acceptance Testing (UAT)

Answer 8

Testing conducted to determine whether a system satisfies the acceptance criteria and is acceptable for delivery to end users.

Question 9

[QA] Automated Testing

Answer 9

Testing using tools and scripts to automate repetitive, but necessary, testing tasks.

Question 10

[QA] Load Testing

Answer 10

Testing the system’s ability to handle a specified amount of load or traffic.

Question 11

[QA] Performance Testing

Answer 11

Testing the system’s performance characteristics, such as response time, speed, and stability.

Question 11

[QA] Scalability Testing

Answer 11

Testing to ensure that the application can handle an increase in the number of users or load.

Question 12

[QA] Boundary Testing

Answer 12

Testing at the edges or boundaries of the input domain to ensure system stability. Ex: a number field only accepts numbers 1-50. You will want to test if -5, 0, 1, 25, 50, and 100 would work with the expectation of -5, 0, and 100 to not work

Question 13

[QA] Ad Hoc Testing

Answer 13

Informal testing without predefined test cases; often exploratory in nature. This would be you just poking around the application.

Question 14

[QA] Bug Tracking System

Answer 14

A tool used to track defects, issues, or bugs throughout their lifecycle. (Jira, TFS)

Question 15

[QA] Traceability Matrix

Answer 15

A document or table that helps determine all the possible outcomes and the most efficient test coverage

Question 16

[QA] Dynamic Testing

Answer 16

Testing technique where the code is executed to demonstrate the actual behavior of the system.

Question 17

[QA] Static Testing

Answer 17

Testing technique where the code is not executed; it can include reviews and inspections.

Question 18

[QA] Test Environment

Answer 18

The setup of software and hardware for testing, including servers, databases, and network configurations. Note there is usually a Dev, Test, Stage, and Prod environments.
Prod Environments are the live code the users use. Everything else is internal.

Question 19

[QA] Test Suite

Answer 19

Test suites are the logical grouping or collection of test cases to run a single job with different test scenarios.

Question 20

[QA] Negative Testing

Answer 20

A test strategy that ensures that your application can gracefully handle invalid input or unexpected user behavior. For example, if a user tries to type a letter in a numeric field, the correct behavior in this case would be to display the “Incorrect data type, please enter a number” message.

Question 21

[QA] Severity

Answer 21

How badly the defect has affected the application’s functionality.

Ranked 0 -5 (0 being the highest)

A severity of 0 means this needs to be fixed now.

Question 22

[QA] Priority

Answer 22

The order in which developers will fix defects (because priority describes business importance).

Ranked 0-5 (0 being the highest)

Question 23

[QA] Repro Rate (Reproduction rate)

Answer 23

The rate at which the bug/defect can be reproduced. Typically when a bug is found I will test it 5 times, so I know the repro rate (it is rare that I test it more than 10 times)

example Rate: 1/5 meaning it can be reproduced 20% of the time, 5/5 meaning it can be repro’d 100% of the time

Question 24

[Agile] Agile

Answer 24

A set of principles for software development that prioritizes flexibility, collaboration, and customer satisfaction.

Question 25

[Agile] Scrum

Answer 25

An Agile framework that defines roles, events, and artifacts for effective project management.

Question 26

[Agile] Sprint

Answer 26

A time-boxed iteration of work in Scrum, usually 2-4 weeks long, during which a potentially shippable product increment is created.

Question 27

[Agile] Product Owner

Answer 27

The person responsible for defining and prioritizing the product backlog, representing the customer's needs, and making decisions about what to build.

Question 28

[Agile] Scrum Master

Answer 28

A facilitator and coach who helps the Scrum team follow the Agile principles and practices and removes impediments to progress.

Question 29

[Agile] Scrum Team

Answer 29

A cross-functional team consisting of developers, a product owner, and a Scrum Master, responsible for delivering a potentially shippable product increment at the end of each sprint.

Question 30

[Agile] Product Backlog

Answer 30

A prioritized list of features, enhancements, and bug fixes that make up the work to be done on a project.

Question 31

[Agile] User Story

Answer 31

A brief, user-centric description of a feature or functionality, often written from the perspective of an end user.

Question 32

[Agile] Daily Standup (Daily Scrum)

Answer 32

A short, daily meeting where team members discuss their progress, plans, and any impediments they are facing.

Question 32

[Agile] Velocity

Answer 32

A measure of the amount of work completed by a team in a sprint, used for estimating future work and improving planning accuracy.

Question 33

[Agile] Burndown Chart

Answer 33

A visual representation of the amount of work remaining in a sprint or project, helping teams track their progress.

Question 34

[Agile] Acceptance Criteria (AC)

Answer 34

A set of criteria that must be met for a product increment to be considered complete and potentially shippable.

Question 35

[Agile]Backlog Grooming (Refinement)

Answer 35

The process of reviewing, prioritizing, and refining items in the product backlog to ensure they are ready for inclusion in upcoming sprints.

Question 36

[Agile] Sprint Retrospective (Retro)

Answer 36

A meeting held at the end of a sprint for the team to reflect on their process and identify areas for improvement.

Question 37

[Agile] Continuous Integration

Answer 37

The practice of frequently merging code changes into a shared repository, with automated builds and tests to catch integration issues early.

Question 38

[Agile] Story points

Answer 38

Units of measure for expressing an estimate of the overall effort required to fully implement a product backlog item or any other piece of work. This is the combined effort between the Scrum team. Usually set in the fibonacci sequence 0,1,2,3,5,8,13