Software Testing Types

35. What is ad hoc testing in Software Testing?
A: Ad hoc testing is a testing approach; it is the least formal testing approach.
Another Definition Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.

36. What is gamma testing in Software Testing?
A: Gamma testing is testing of software that has all the required features, but it did not go through all the in-house quality checks. Cynics tend to refer to software releases as "gamma testing".

37. What is functional testing in Software Testing?
A: Functional testing is same as black box testing. Black box testing a type of testing that considers only externally visible behavior. Black box testing considers neither the code itself, nor the "inner workings" of the software.

38. What is closed box testing in Software Testing?
A: Closed box testing is same as black box testing. Black box testing a type of testing that considers only externally visible behavior. Black box testing considers neither the code itself, nor the "inner workings" of the software.

39. What is bottom-up testing in Software Testing?
A: Bottom-up testing is a technique for integration testing. A test engineer creates and uses test drivers for components that have not yet been developed, because, with bottom-up testing, low-level components are tested first. The objective of bottom-up testing is to call low-level components first, for testing purposes.

40. How do you perform integration testing in Software Testing?
A: First, unit testing has to be completed. Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team. Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.



41. When do you choose automated testing in Software Testing?
A: For larger projects, or ongoing long-term projects, automated testing can be valuable. But for small projects, the time needed to learn and implement the automated testing tools is usually not worthwhile. Automated testing tools sometimes do not make testing easier. One problem with automated testing tools is that if there are continual changes to the product being tested, the recordings have to be changed so often, that it becomes a very time-consuming task to continuously update the scripts. Another problem with such tools is the interpretation of the results (screens, data, logs, etc.) that can be a time-consuming task. You can learn to use automated tools, with little or no outside help.

42. What is the difference between system testing and integration testing in Software Testing?
A: System testing is high level testing, and integration testing is a lower level testing. Integration testing is completed first, not the system testing. In other words, upon completion of integration testing, system testing is started, and not vice versa. For integration testing, test cases are developed with the express purpose of exercising the interfaces between the components. For system testing, on the other hand, the complete system is configured in a controlled environment, and test cases are developed to simulate real life scenarios that occur in a simulated real life test environment. The purpose of integration testing in Software Testing is to ensure distinct components of the application still work in accordance to customer requirements. The purpose of system testing, on the other hand, is to validate an application's accuracy and completeness in performing the functions as designed, and to test all functions of the system that are required in real life.

43. What are the parameters of performance testing in Software Testing?
A: The term 'performance testing' is often used synonymously with stress testing, load testing, reliability testing, and volume testing. Performance testing is a part of system testing, but it is also a distinct level of testing. Performance testing verifies loads, volumes, and response times, as defined by requirements.



44. What is disaster recovery testing in Software Testing?
A: Disaster recovery testing is testing how well the system recovers from disasters, crashes, hardware failures, or other catastrophic problems

45. Which of the tools should learn?
A:Learn the most popular software tools (i.e. LabView, LoadRunner, Rational Tools, Winrunner, etc.) -- and you want to pay special attention to LoadRunner and the Rational Toolset.

46.What is the objective of regression testing in Software Testing?
A: The objective of regression testing is to test that the fixes have not created any other problems elsewhere. In other words, the objective is to ensure the software has remained intact. A baseline set of data and scripts are maintained and executed, to verify that changes introduced during the release have not "undone" any previous code. Expected results from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.

47.Is the regression testing performed manually in Software Testing?
A: It depends on the initial testing approach. If the initial testing approach is manual testing, then, usually the regression testing is performed manually. Conversely, if the initial testing approach is automated testing, then, usually the regression testing is performed by automated testing.

48. What is Exploratory testing in Software Testing?
Often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.

49. What is Volume testing in Software Testing?
Volume testing involves testing a software or Web application using corner cases of "task size" or input data size. The exact volume tests performed depend on the application's functionality, its input and output mechanisms and the technologies used to build the application. Sample volume testing considerations include, but are not limited to:
If the application reads text files as inputs, try feeding it both an empty text file and a huge (hundreds of megabytes) text file.
If the application stores data in a database, exercise the application's functions when the database is empty and when the database contains an extreme amount of data.
If the application is designed to handle 100 concurrent requests, send 100 requests simultaneously and then send the 101st request.
If a Web application has a form with dozens of text fields that allow a user to enter text strings of unlimited length, try populating all of the fields with a large amount of text and submit the form.

50. What is Sociability Testing in Software Testing?
This means that you test an application in its normal environment, along with other standard applications, to make sure they all get along together; that is, that they don't corrupt each other's files, they don't crash, they don't consume system resources, they don't lock up the system, they can share the printer peacefully, etc.

51. What is Mutation testing in Software Testing?
. A method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

Back