602 Software Testing 3 Marks Questions with Answer

1.              FTR

Ans. : Formal Technical Review (FTR) is a software quality control activity performed by software engineers. Objectives of formal technical review (FTR): Some of these are: Useful to uncover error in logic, function and implementation for any representation of the software.

2.              STLC

Ans. : Software Testing Life Cycle (STLC) model is basically developed to identify which testing activities needs to be carried and what's the best time to perform them to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.

3.              Waterfall model

Ans. : The Waterfall Model approach is the most basic life cycle model. This is the first Process Model begins and used broadly in Software Development to ensure project success. This model was developed by Winston Royce in the early 1970. Waterfall model is software development process sequential process, as flowing progressively downwards like waterfall through multiple phases.

4.              Walkthrough

Ans. : Walkthroughs can be viewed as presentation reviews in which a review participant, usually the developer of the software being reviewed, narrates a description of the software and the remainder of the review group provides their feedback throughout the presentation. These are referred to as presentation reviews because the bulk of the feedback usually only occurs for the material actually presented at the level it is presented.

5.              Code Review

Ans. : Code Review is a systematic examination, which can find and remove the vulnerabilities in the code such as memory leaks and buffer overflows.
1. Technical reviews are well documented and use a well-defined defect detection process that includes peers and technical experts. 2. It is ideally led by a trained moderator, who is NOT the author. 3. This kind of review is usually performed as a peer review without management participation. 4. Reviewers prepare for the review meeting and prepare a review report with a list of findings. 5. Technical reviews may be quite informal or very formal and can have a number of purposes but not limited to discussion, decision making, evaluation of alternatives, finding defects and solving technical problems.

 

6.              State transition

Ans. : This testing is used where some aspect of the system can be described in what is called a 'finite state machine'. This simply means that the system can be in a (finite) number of different states, and the transitions from one state to another are determined by the rules of the 'machine'. This is the model on which the system and the tests are based.

Any system where you get a different output for the same input, depending on what has happened before, is a finite state system.

One of the advantages of the state transition technique is that the model can be as detailed or as abstract as you need it to be. Where a part of the system is more important (that is, requires more testing) a greater depth of detail can be modeled. Where the system is less important (requires less testing), the model can use a single state to signify what would otherwise be a series of different states.

7.              Decision table

Ans. : A decision table is a good way to deal with different combination inputs with their associated outputs and also called cause-effect table. Reason to call a cause-effect table is an associated logical diagramming technique called cause-effect graphing that is basically used to derive the decision table. We can apply Equivalence Partitioning and Boundary Value Analysis techniques to only specific conditions or inputs. Although, if we have dissimilar inputs that result in different actions being taken or secondly we have a business rule to test that there are different combinations of inputs which result in different actions.

8.              Cause Effect

Ans. : Cause Effect Graphing based technique is a technique in which a graph is used to represent the situations of combinations of input conditions. The graph is then converted to a decision table to obtain the test cases. Cause-effect graphing technique is used because boundary value analysis and equivalence class partitioning methods do not consider the combinations of input conditions. But since there may be some critical behaviour to be tested when some combinations of input conditions are considered, that is why cause-effect graphing technique is used.

9.              Behavioral Testing

Ans. : Software testing involves the use of various techniques and tools to evaluate a software program and determine its results and outputs through several use cases. Behavior testing in software testing is an example of a technique we can use to validate certain behaviors of a software program instead of the technical perspective, under various circumstances. Behavior testing helps determine how the system must behave externally. It is also known as black box testing.

10.            Execution Testing

Ans. : In the White box testing the main part is the Code Coverage analysis which helps to identify the gaps in a test case. It allows you to find the area in the code to which is not executed by a given set of test cases. Upon identifying the gap in the test case suite you can add the respective test case. So it helps to improve the quality of the oftware application. The adequacy of the test cases is often measured with a metric alled coverage. Coverage is a measure of the completeness of the set of test cases.

a) Segment/Statement Coverage: Ensure that each code statement is executed once.

b) Branch Coverage or Node Testing: Coverage of each code branch in from all possible ways.

c) Compound Condition Coverage: For multiple conditions, test each condition with multiple paths and combination of different paths to reach that condition.

d) Basis Path Testing (Path Coverage): Each independent path in the code is taken for testing.

11.            Mutation Testing

Ans. : In this type of testing, the application is tested for the code that was modified after fixing a particular bug/defect. It also helps in finding out which code and which strategy of coding can help in developing the functionality effectively. Besides all the testing types given above, there are some more types which fall under both Black box and White box testing strategies such as: Functional testing (which deals with the code in order to check its functional performance), Incremental integration testing (which deals with the testing of newly added code in the application), Performance and Load testing (which helps in finding out how the particular code manages resources and give performance etc.).

12.            Top-Down integration

Ans. : Top-down testing is a type of incremental integration testing approach in which testing is done by integrating or joining two or more modules by moving down from top to bottom through control flow of architecture structure. In these, high-level modules are tested first, and then low-level modules are tested. Then, finally, integration is done to ensure that system is working properly. Stubs and drivers are used to carry out this project. This technique is used to increase or stimulate behavior of Modules that are not integrated into a lower level.

13.            Beta Testing

Ans. : Beta Testing is performed by real users of the software application in a real environment. Beta testing is one of the types of User Acceptance Testing. A Beta version of the software, whose feedback is needed, is released to a limited number of end-users of the product to obtain feedback on the product quality. Beta testing helps in minimization of product failure risks and it provides increased quality of the product through customer validation. It is the last test before shipping a product to the customers. One of the major advantages of beta testing is direct feedback from customers.

14.            Stub

Ans. : A stub is a small piece of code that takes the place of another component during testing. The benefit of using a stub is that it returns consistent results, making the test easier to write. And you can run tests even if the other components are not working yet.

15.            Module Testing

Ans. : A software application contains an integration of various modules. Modules are programs written in a specific language consisting of subprograms, subroutines, functions, classes, and procedures. Module testing is a process where you need to test each unit of these modules to ensure they adhered to the best coding standards. Unless a module passes the testing phase, it cannot go for the application testing process.

Module testing, aka component testing, helps to early detection of errors in application testing. This can be a massive relief for testers during the later stage of testing. Module testing is a gateway to parallel testing that allows testers to test multiple modules simultaneously.

16.            Performance Testing

Ans. : Performance Testing is a type of software testing that ensures software applications to perform properly under their expected workload. It is a testing technique carried out to determine system performance in terms of sensitivity, reactivity and stability under a particular workload.

Performance Testing is the process of analyzing the quality and capability of a product. It is a testing method performed to determine the system performance in terms of speed, reliability and stability under varying workload. Performance testing is also known as Perf Testing.

17.            Smoke Testing

Ans. : Smoke Testing is a software testing method that determines whether the employed build is stable or not. It acts as a confirmation of whether the quality assurance team can proceed with further testing. Smoke tests are a minimum set of tests run on each build. Smoke testing is a process where the software build is deployed to a quality assurance environment and is verified to ensure the stability of the application.

18.            Software Metrics

Ans. :    Software testing metrics are quantifiable indicators of the software testing process progress, quality, productivity, and overall health. The purpose of software testing metrics is to increase the efficiency and effectiveness of the software testing process while also assisting in making better decisions for future testing by providing accurate data about the testing process. A metric expresses the degree to which a system, system component, or process possesses a certain attribute in numerical terms. A weekly mileage of an automobile compared to its ideal mileage specified by the manufacturer is an excellent illustration of metrics.

19.            Lines of Code

Ans. : A line of code (LOC) is any line of text in a code that is not a comment or blank line, and also header lines, in any case of the number of statements or fragments of statements on the line. LOC clearly consists of all lines containing the declaration of any variable, and executable and non-executable statements. As Lines of Code (LOC) only counts the volume of code, you can only use it to compare or estimate projects that use the same language and are coded using the same coding standards. 

20.            Function Point

Ans. : FPA provides a standardized method to functionally size the software work product. This work product is the output of software new development and improvement projects for subsequent releases. It is the software that is relocated to the production application at project implementation. It measures functionality from the user’s point of view i.e. on the basis of what the user requests and receives in return.

Function Point Analysis (FPA) is a method or set of rules of Functional Size Measurement. It assesses the functionality delivered to its users, based on the user’s external view of the functional requirements. It measures the logical view of an application, not the physically implemented view or the internal technical view.

21.            Product Metrics

Ans. : Product metrics are software product measures at any stage of their development, from requirements to established systems. Product metrics are related to software features only. Product metrics fall into two classes:

Dynamic metrics that are collected by measurements made from a program in execution.

Static metrics that are collected by measurements made from system representations such as design, programs, or documentation.

Dynamic metrics help in assessing the efficiency and reliability of a program while static metrics help in understanding, understanding and maintaining the complexity of a software system.

22.            System Testing

Ans. : System Testing is a type of software testing that is performed on a complete integrated system to evaluate the compliance of the system with the corresponding requirements. In system testing, integration testing passed components are taken as input. The goal of integration testing is to detect any irregularity between the units that are integrated together. System testing detects defects within both the integrated units and the whole system. The result of system testing is the observed behavior of a component or a system when it is tested. System Testing is carried out on the whole system in the context of either system requirement specifications or functional requirement specifications or in the context of both.

23.            Security Testing

Ans. : The software industry has achieved solid recognition in this age. In recent decades, however, the cyber-world seems to be an even more dominating and driving force which is shaping up the new forms of almost every business.

Web-based ERP systems used today are the best evidence that IT has revolutionized our beloved global village. These days, websites are not only meant for publicity or marketing but they have evolved into stronger tools to cater to complete business needs.

24.            GUI Checklist

Ans. : User interface testing, a testing technique used to identify the presence of defects is a product/software under test by using Graphical user interface [GUI]. GUI is a hierarchical, graphical front end to the application, contains graphical objects with a set of properties. During execution, the values of the properties of each objects of a GUI define the GUI state. It has capabilities to exercise GUI events like key press/mouse click. Able to provide inputs to the GUI Objects. To check the GUI representations to see if they are consistent with the expected ones. It strongly depends on the used technology.

25.            Apache Jmeter

Ans. : JMeter is a software that can perform load test, performance-oriented business (functional) test, regression test, etc., on different protocols or technologies.

Stefano Mazzocchi of the Apache Software Foundation was the original developer of JMeter. He wrote it primarily to test the performance of Apache JServ (now called as Apache Tomcat project). Apache later redesigned JMeter to enhance the GUI and to add functional testing capabilities.

JMeter is a Java desktop application with a graphical interface that uses the Swing graphical API. It can therefore run on any environment / workstation that accepts a Java virtual machine, for example − Windows, Linux, Mac, etc.

26.            Load Runner

Ans. : LoadRunner is a software testing tool from Micro Focus. It is used to test applications, measuring system behaviour and performance under load. LoadRunner can simulate thousands of users concurrently using application software, recording and later analyzing the performance of key components of the application

27.            Vusers

Ans. : The Virtual User (Vuser) concept enables testers to run the test cases in form of virtual users thus minimizing manual intervention. There is no limitation on the number of Vusers that can be created if the appropriate license is obtained as per requirements. All the Vusers can be controlled from a single dashboard.

28.            Scenario

Ans. : The test scenario is a detailed document of test cases that cover end to end functionality of a software application in liner statements. The liner statement is considered as a scenario. The test scenario is a high-level classification of testable requirements. These requirements are grouped on the basis of the functionality of a module and obtained from the use cases.

In the test scenario, there is a detailed testing process due to many associated test cases. Before performing the test scenario, the tester has to consider the test cases for each scenario.