Тест по теории тестирования (en)

Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. This method of test can be applied virtually to every level of software testing: unit, integration, system and acceptance. It is sometimes referred to as specification-based testing.

It is a method of installing changes to an application or server by swapping alternating production and staging servers. In this method, two identical production environments work in parallel.

One is the currently-running production environment receiving all user traffic (Blue). The other is a clone of it, but idle (Green). Both use the same database backend and app configuration.

The new version of the application is deployed in the green environment and tested for functionality and performance. Once the testing results are successful, application traffic is routed from blue to green. Green then becomes the new production.

If there is an issue after green becomes live, traffic can be routed back to blue.

It is a method of installing changes to an application or server by swapping alternating production and staging servers. In this method, two identical production environments work in parallel.

One is the currently-running production environment receiving all user traffic (Blue). The other is a clone of it, but idle (Green). Both use the same database backend and app configuration.

The new version of the application is deployed in the green environment and tested for functionality and performance. Once the testing results are successful, application traffic is routed from blue to green. Green then becomes the new production.

If there is an issue after green becomes live, traffic can be routed back to blue.

It is a software testing technique that divides the input data of a test into partitions of equivalent data from which test cases can be derived.
This comes under the Black-box testing technique.
Here the test data is divided into partitions and the test cases are designed to cover each partition at least once.

It is a software testing technique that divides the input data of a test into partitions of equivalent data from which test cases can be derived. This comes under the Black-box testing technique. Here the test data is divided into partitions and the test cases are designed to cover each partition at least once.

In White box testing the internal structure, code, design and implementation of the application/product is known to the tester. This type of testing is named so because the tester can see inside the system.

Bucket testing (also called A/B testing or Split testing) is a type of testing where two versions of a website are tested and compared against one another to see which one performs better on specified key metrics (such as clicks, downloads or purchases).

Accessibility Testing is a subset of Usability testing to ensure the system or component is usable by people having disabilities.

Accessibility Testing is a subset of Usability testing to ensure the system or component is usable by people having disabilities.

Priority is determined by the impact of the bug on the business. For example, if on the Google home page an ‘o’ is missing from the word ‘Google’, it does not impact any functionality but can impact the name and business and therefore this bug will be of higher priority.

Severity is determined by the functional impact of the bug or impact on the application. For example, if a very commonly used button on the homepage of a website does not work, it is a bug of critical severity. Whereas if there is some spelling mistake in a disclaimer text which is present on the last page and is rarely seen by the user, then it will be of trivial severity.