FAQs on QA Testing

Get some FAQs on QA Testing and practice it

What does Test Strategy include?

It includes introduction, Test Objectives, Test Process, Test Methodology, Test Scope, Release Criteria for Testing (exit criteria), Test Lab configuration, resource and schedule for test activities, acceptance criteria, test environment, test tools, test priorities, test planning, executing a test pass and types of test to be performed.

What are different types of software testing and define them?

Different types of testing are:

1) Unit testing

2) Shakeout testing

3) Smoke testing (Ad-hoc testing)

4) Functional testing

5) Integration testing

6) Regression testing

7) System testing

8) Load testing

9) Stress testing

10) Performance testing

11) User acceptance testing

12) Black box testing

13) White box testing

14) Alpha testing

15) Beta testing

(Note: Except the Shakeout testing and Unit testing (which are respectively done by the CMT (Configuration Management Team) and Coder/Developer), all other testing are done by the QA tester.)

What is Unit testing?

It is a test to check the code whether it is properly working or not as per the requirement.

What is Shakeout testing?

This test is basically carried out to check the networking facility, database connectivity and the integration of modules. The Configuration Management team, who prepare builds for test environments, normally does this test. They also test whether the major components of the software are not broken. This test is done BEFORE the build is deployed in the test environment. After the shakeout testing, the next step is smoke testing (which is done by the testers after the build is deployed in the test environment)

What is smoke testing?

This test is done when the build is just prepared (fresh build) and deployed in the test environments. This is basically an ad hoc test to check roughly to make sure the major functionalities are not broken. It is the preliminary a test carried out by the QA tester. After the smoke test, the testers perform functional testing.

What is Functional testing?

It is a test to check whether each and every function of that application is working as per the requirement (remember this work “as per requirement document”-you must say this in the interview). It is a major test where 80% of the tests are done. In this test, the Test Cases are executed (or run).

What is Integration testing?

 It is a test to check whether all the modules are combined together or not and working successfully as specified in the requirement document. (Just for your information: Each developer works on different modules. When they finish their code, the configuration management team puts them together and prepares a build. We, as testers, need to make sure that these modules, which are now combined, work as per requirement document)

What is Regression testing?

When a new functionality is added to the software, we need to make sure that the added new functionality does not break the other parts of the application. Or when defects (bugs) are fixed, we need to make sure that the bug fix has not broken the other parts of the application. To test this, we perform a repetitive test, which is called regression test.

What is System testing?

When testers complete testing (The testers test the application in the test environments, meaning they test with the test data only, NOT with the real data), the application (software) has to be tested in the real environment. What it means is, since the testers test it in the test environment with the test data, we have to make sure that the application works well in the real environment with the real data. In test environment, some of the things cannot be simulated or tested. Al though the test environment is very similar to the production (real) environment, we need to make sure that we get a smooth delivery in the real system as well (As servers are different and database is different, things may not work as expected when the application is moved from test environment to production environment)

What is Load testing?

It is a test to check the user’s response time for number of users using any one scenario (single business process) of the same application at the same time.

What is Performance testing?

 It is a test to check the user’s response time for number of users using multiple scenarios (multiple business process) of the same application at the same time.

(Did you notice the difference between Load Testing and Performance testing? What is it? See the highlighted bold letters)

What is Stress testing?

In this type of testing the application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand.

What is User acceptance testing (UAT)?

In this type of testing, the software is handed over to the user in order to find out if the software meets the user expectations and works as it is expected to. In this testing, the tester may do the testing or the clients may have their own testers (For example, banks may have their own teller employees who can test the application).

What is Black box testing?

It is test where a tester performs testing without looking into the code. (OR it is a testing method where the application under test is viewed as a black box and the internal behavior of the program is completely ignored. Testing occurs based upon the external specifications. Also known as behavioral testing, since only the external behavior of the program is evaluated and analyzed.)

What is White box testing?

It is a test where a tester looks into the code and performs the testing.

What is Alpha testing?

In this type of testing, the users are invited at the development center where they use the application and the developers note every particular input or action carried out by the user. Any type of abnormal behavior of the system is noted and rectified by the developers.

What is Beta testing?

In this type of testing, the software is distributed as a beta version to the users and users test the application at their sites. As the users explore the software, in case if any exception/defect occurs that is reported to the developers.