Quality Assurance (QA) module 3

smoke test

A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.

Critical path test

Test cases that cover the functionality used most of the time by the majority of users.

Extended test

Test cases that cover the "nice-to-have" functionality (not used most of the time by the majority of users).

Re-testing

Also known as Confirmation testing. Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.

regression testing

A type of change-related testing to detect whether defects have been introduced or uncovered in unchanged areas of the software.

black-box testing

A test approach based on the specification of a component or system.

grey-box testing

A test approach that combines elements of black-box testing and white-box testing.

white-box testing

A test approach based on the internal structure of a component or system.

functional testing

A test type to determine the functional suitability of a test object.

non-functional testing

A test type to evaluate that a component or system complies with non-functional requirements.

Manual Testing

In Manual Testing , testers manually execute test cases without using any automation tools.

Automated Testing

Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

Positive Testing

This determines that your application works as expected.

Negative Testing

Ensures the application can gracefully handle invalid input or unexpected user behavior.

destructive testing

A test type that subjects a component or system to malicious inputs, abnormal conditions, or security exploits to induce persistent anomalous behavior.

static testing

A test approach that does not involve the execution of a test item.

dynamic testing

A test approach that involves test execution of a test item.

scripted testing

A test approach that involves the creation and use of a test script.

exploratory testing

A test approach in which tests are dynamically designed and executed based on tester's knowledge, exploration of a test item, and previous test results.

ad hoc testing

Informal testing performed without test analysis and test design.

Installation Testing

testing software as it is installed and first operated

usability testing

Testing to evaluate the degree to which the system can be used by specified users with effectiveness, efficiency and satisfaction in a specified context of use.

Accessibility Testing

Testing to determine the ease by which users with disabilities can use a component or system.

security testing

A test type to determine the security of a component or system.

Internationalization testing

Internationalization testing verifies that software can be adapted to various languages and regions without engineering changes;

Localization Testing

Localization testing verifies that software is (can be) adapted to a particular culture/locale; Things that are often changed because localization, such as the: ● User Interface and content files. ● Keyboards

Compatibility Testing

done to verify that the web site works with a variety of browsers and browser versions

Configuration Testing

Check that the program performs adequately on the recommended configurations.

Cross-Browser Testing

Testing on different browsers.

Cross-Platform Testing

The process of testing sites on a variety of computer hardware and software configurations

Reliability Testing

Consistency of test results over time.

recoverability testing

Testing to determine the recoverability of a software product.

Failover Testing

Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained (e.g., function availability or response times).

performance testing

A test type to determine the performance efficiency of a component or system.

load testing

A type of performance testing to evaluate the behavior of a component or system under varying loads, usually between anticipated conditions of low, typical, and peak usage.

scalability testing

Testing to determine the scalability of the software product.

Volume Testing

testing the application with a large amount of data

Stress Testing

A type of performance testing to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced availability of resources such as access to memory or servers.

concurrency testing

Testing to evaluate if a component or system involving concurrency behaves as specified.