Software QA Concepts Review

Questions and Answers

What is the primary focus of unit testing in software development?

Testing the integration of new components with existing ones

Testing individual units of code, such as classes and modules (correct)

Ensuring the application meets customer-facing environment requirements

Verifying business logic and requirements

Which type of testing involves verifying that an application meets business needs and works as intended in a customer-facing environment?

Stress testing

Performance testing

Smoke testing

Acceptance testing (correct)

What is the primary difference between performance testing and stress testing?

Performance testing is done by developers, while stress testing is done by QA engineers

Performance testing focuses on metrics, while stress testing focuses on functionality

Stress testing involves overloading the application, while performance testing focuses on normal usage (correct)

Performance testing is a type of stress testing

Which type of testing is typically done by project/product managers and UAT as a formal step to accept tested items into final release or deployment?

Acceptance testing Signup and view all the answers

What is the primary focus of smoke testing in software development?

Quickly testing the basic functionality of an application Signup and view all the answers

What is the primary focus of regression testing?

To verify that previously integrated components continue to work as intended Signup and view all the answers

What type of testing should be done first in a project?

Unit testing Signup and view all the answers

What is the purpose of a test plan?

To provide transparency to product management on how testing will be done Signup and view all the answers

What is a requirement for every test case?

To have preconditions that need to happen or exist before the test is executed Signup and view all the answers

What type of testing is used to ensure that UI components match the visual mock-up design?

UI testing Signup and view all the answers

Study Notes

Software QA

Verification and validation of software functionality to ensure developed software matches client needs.

Types of Testing

Unit Testing: Developing code that specifically tests functionality of particular parts (units) of an application, done at a low level at the source of the application, focuses on testing classes, modules, components, variables, etc.
Integration Testing: Testing that ensures new components added to an application work as intended with existing components.
Functional Testing: Verifies business logic/requirements and proper function of an application depending on stated/documented/intended behavior.
Acceptance Testing: Verifies system and functionalities within it work according to business need, usually done by project/product managers and UAT.
Smoke Testing: Quick tests performed to check basic functionality of an application, focusing on major features of the application.
Performance Testing: Tests application's ability to handle heavy loads of requests and the velocity at which it can process them, usually resulting in metrics.
Stress Testing: Tests application's ability to perform properly while under heavy loads, usually done by overloading the amount of requests that the application can process.
Regression Testing: A suite of tests performed to check that previously integrated components of the application continue to work as intended, differs from integration testing.
UI Testing: Ensures UI components match visual mock-up design for the application, implies testing correct width/height of web elements, colors, and element-to-element alignment.
Exploratory Testing: Tests in which no documentation exists, done to get an idea of what needs to be tested, documented, and focused on in an application.

Building a Test Plan

The Testing Pyramid: The order of testing - unit tests, then functional tests, then UI tests, due to the level of application development.
Test Plan: Documentation that describes how a test will be done, what the purpose is of testing, when something will be tested, and what the expected result of the testing will be.
Test Cases: Documentation on how to execute a test, must include:
- Preconditions: Things that need to happen or exist before the test is actually executed.
- Tools for documenting test cases exist, such as TestRail, AzureDevops, and XRay.