QA Testing Types

Question 1

Black Box testing

Answer 1

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.

Question 2

White Box testing

Answer 2

White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of software testing that tests internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing). In white-box testing, an internal perspective of the system, as well as programming skills, are used to design test cases.

Question 3

Grey Box testing

Answer 3

Gray-box testing (International English spelling: grey-box testing) is a combination of white-box testing and black-box testing. The aim of this testing is to search for the defects if any due to improper structure or improper usage of applications.

Question 4

Functional Testing

Answer 4

Functional testing is a quality assurance (QA) process[1] and a type of black-box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered (unlike white-box testing).[2] Functional testing is conducted to evaluate the compliance of a system or component with specified functional requirements.[3] Functional testing usually describes what the system does.

Question 5

Non-functional testing

Answer 5

This is in contrast to functional testing, which tests against functional requirements that describe the functions of a system and its components. The names of many non-functional tests are often used interchangeably because of the overlap in scope between various non-functional requirements. For example, software performance is a broad term that includes many specific requirements like reliability and scalability.

Question 6

Exploratory testing

Answer 6

While the software is being tested, the tester learns things that together with experience and creativity generates new good tests to run. Exploratory testing is often thought of as a black box testing technique. Instead, those who have studied it consider it a test approach that can be applied to any test technique, at any stage in the development process. The key is not the test technique nor the item being tested or reviewed; the key is the cognitive engagement of the tester, and the tester’s responsibility for managing his or her time.

Question 7

Smoke testing

Answer 7

Smoke Testing is a software testing process that determines whether the deployed software build is stable or not. Smoke testing is a confirmation for QA team to proceed with further software testing. It consists of a minimal set of tests run on each build to test software functionalities. Smoke testing is also known as “Build Verification Testing” or “Confidence Testing.”

In simple terms, we are verifying whether the important features are working and there are no showstoppers in the build that is under testing.

Question 8

Regression testing

Answer 8

Re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. (Functional)

Question 9

Manual testing

Answer 9

Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end-user whereby they use most of the application’s features to ensure correct behavior. To guarantee the completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases

Question 10

Automation testing

Answer 10

In software testing, test automation is the use of software separate from the software being tested to control the execution of tests and the comparison of actual outcomes with predicted outcomes.

Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place, or perform additional testing that would be difficult to do manually. Test automation is critical for continuous delivery and continuous testing

Question 11

Unit testing

Answer 11

is performed by the developer. The goal of Unit testing is to isolate each part of the program, and show that individual parts are correct. (Functional)

Question 12

System or End to End Testing

Answer 12

to test the whole application. The purpose of this test is to evaluate the system’s compliance with the specified requirements. (Functional)

Question 13

Acceptance testing

Answer 13

to test the application before the final release. Usually performed, using UAT test case
(Functional

Question 14

Performance/load/ and stress testing

Answer 14

usually is done using an automation tool.
Performance testing is considered as one of the important and mandatory testing types in terms of the following aspects −
Speed (i.e. Response Time, data rendering, and accessing)
Capacity
Stability
Scalability
(Non-Functional)

Question 15

Load testing

Answer 15

his type of testing identifies the maximum capacity of software and its behavior at peak time.

Question 16

Stress testing

Answer 16

includes testing the behavior of the software under abnormal conditions.

Examples:to test under conditions with extreme workloads, insufficient memory, diminished shared resources, or unavailable software services or hardware

Question 17

Usability testing

Answer 17

how user-friendly the application is.

Question 18

Security testing

Answer 18

to make sure that nonauthorized user is unable to access the site.

Also, that password and social security number are encrypted

Pay attention to https:// in the url/address