Software Testing MCQ

Answer: (a) Breadth test and depth test

Explanation: The maintenance testing is performed during the development, migration, and modification cycle. It is done on the previously deployed software where its needs to be improved, altered or migrated to other hardware.

Answer: (d) Project Initiation Note [PIN]

Explanation: The test documentation is the document which is created during or before the testing of a software application. The entire test execution process depends on the complication of the test document.

Answer: (a) Evaluating deliverable to find errors

Explanation: Software testing is a process of classifying the correctness of software by seeing its all attributes and assessing the execution of software components to find the software bugs or errors.

Answer: (d) Testing Closure

Explanation: SDLC defines various phases of software development and the order of execution of phases. Software development life cycle is a process that creates a structure for the development of software.

Answer: (a) Structural Testing

Explanation: Structural testing is also known as a White box or Clear box, or Glass box testing. In structural testing, we can understand what is happening inside the application or the software.

Answer: (c) Black Box testing

Explanation: Boundary value analysis is one of the widely used case design techniques for black-box testing. It is used to test boundary values because the input values near the boundary have higher chances of error. Boundary values are those that contain the upper and lower limit of a variable.

Answer: (d) Test Type

Explanation: It is a type of software testing, which is used to verify the functionality of the software application, whether the function is working according to the requirement specification. It is performed as black-box testing, which verifies the functionality of the application.

Answer: (d) All of the above

Explanation: Integration, Unit and System testing are various testing levels where the Unit testing is used to test each unit or an individual component of the software application.

The integration testing is used only after the functional testing is completed on each module of the application. And system testing is end-to-end testing, where the testing environment is similar to the production environment.

Answer: (b) Requirement Gathering

Explanation: The software testing procedure is also known as Software Testing Life Cycle (STLC), which contains various phases of the testing process. And all activities are done to improve the quality of the software product.

Answer: (b) Test Execution level

Explanation: As soon as the bug fixes are done, we will perform the Sanity testing. It is narrow, deep. Sanity testing's primary objective is to ensure that all the defects have been fixed and no further issues come into existence due to these changes.

Answer: (d) All of the above

Explanation: In software testing, the statement coverage, decision coverage, data flow is part of the white-box testing technique.

Answer: (b) Developer's end

Explanation: Alpha testing is conducted in the organization and tested by a representative group of end-users at the developer's end, where the developers observe the users and write down the problems. Alpha testing is simulated or real operational testing at an in-house site.

Answer: (c) Incident Reports

Explanation: The test plan is a base of every software's testing. It is a detailed document, which describes software testing areas and activities. It outlines the test strategy, objectives, test schedule, required resources (human resources, software, and hardware), test estimation and test deliverables.

Answer: (b) Interface Error

Explanation: Whenever there is a clear relationship between modules, we go for the integration testing. And the main purpose of the integration testing level is to expose the faults at the time of interaction between integrated components or units.

Answer: (a) Experience-based Test Design Technique

Explanation: Whenever the requirement does not exist, we do one round of exploratory testing. In this testing, we will be exploring the application in all possible ways, understanding the application's flow, preparing a test document and then testing the application.

Answer: (d) Both option a & c

Explanation: Regression testing is used to authenticate a code change in the software that does not impact the product's existing functionality. Regression testing can be performed on a new build when there is a significant change in the original functionality. It ensures that the code still works when the changes are occurring.

Answer: (c) The testing team is not good

Explanation: Sometimes, the fundamentals of software testing define that no product has zero bugs.

Answer: (a) White box testing

Explanation: Cyclomatic complexity is a software metric, which is used to measure the complexity of a program. It gives the minimum number of paths that can generate all possible paths through the module.

Answer: (c) Statement testing

Explanation: Testing is a group of techniques to determine the application's correctness under the predefined script, but testing cannot find all the defects in the application. Testing includes an examination of code and the execution of code in various environments, conditions, and all the examining aspects of the code.

Answer: (d) Test Plan

Explanation: The Exit criteria of the functional testing should be followed because the percentage (%) of exit criteria are decided by the meeting with both development and test manager because their collaboration can achieve the percentage. And When all the test cases are executing, most of the test cases must be passed.

Answer: (b) how much regression testing should be done

Explanation: In regression testing, once we understand the new requirements, we will perform one round of impact analysis to avoid the major risk. The impact analysis is done by the customer based on their business knowledge, the developer based on their coding knowledge. Most importantly, it is done by the test engineer because they have product knowledge.

Answer: (c) Black box testing

Explanation: Usability testing is used to checks the defect in the end-user interaction of software or the product. It makes sure that the developed software is easy while using the system without facing any problem and makes end-user life easier.

Answer: (a) Big bang approach

Explanation: The Incremental testing approach is used whenever there is a solid relationship between the dependent modules. In this, modules are added in ascending order one by one or according to need. Generally, two or more than two modules are added and tested to control the correctness of functions.

Answer: (c) User's end

Explanation: Beta testing is an integral part of external user acceptance testing, where real users perform this testing. It is implemented after the alpha testing. Beta testing is the last phase of the testing carried out at the client's or user's end.

Answer: (d) Test case design/ data management techniques

Explanation: When there is no specific method for identifying the error, we go for the Error guessing technique. It is totally based on the experience of the test analyst, where the tester uses the experience to guess the problematic areas of the software.

Answer: (a) After the coding phase

Explanation: Generally, the white box testing was performed after the programming phase because this type of testing required the programming skills to design test cases. The Developers perform the white box testing to test every line of the program's code and then send the application or the software to the testing team for further process.

Answer: (b) Behavioral Testing

Explanation: White box testing is known as glass box testing, structural testing, clear box testing, open box testing and transparent box testing.

Answer: (b) It is based on the nature of the project

Explanation: The Test levels can always be restructured or combined based on n the nature of a project or system planning.

Answer: (b) Its departure from specified behavior

Explanation: In software testing, a software bug can also be issue, error, fault, or failure where lots of defect leads to failure of the software.

Answer: (d) Software development testing (SDLC) model

Explanation: Whenever we have a large and complex application, we go for the V model. In the V model, firstly, all the activities go in the downward direction, and at one point in time, it starts moving in the upward direction, and to re-use the test document for the testing process and forms a V shape.

Answer: (b) Adhoc testing

Explanation: Whenever we have to randomly check the application without following any sequence or procedure, we do one round of Adhoc testing. Since the user doesn't know how to use the application, they may use it randomly and find some issues. Adhoc testing is also known as negative testing because we test the application against the client's requirements.

Answer: (c) Performance testing

Explanation: Non-functional testing is testing where the tester will test the non-functional parameters, for example, performance, reliability, load test, and accountability of the software or application. And Performance testing is testing where we check the behavior of an application by applying some load.

Answer: (a) Boundary value analysis

Explanation: The Black box testing is testing where we examine the software's functionality without looking into its internal structure or coding. And the boundary value analysis is used to test boundary values as the input values near the boundary have higher chances of error. And it is one of the widely used case design techniques for black-box testing.

Answer: (a) Beta testing

Explanation: The user acceptance testing is done once the application is bug-free because no customer accepts the application blindly before using it. Hence, they perform one round of testing for their satisfaction. And Beta testing is one essential part of Acceptance Testing, which is performed before releasing the software.

Answer: (c) White-Box testing

Explanation: The white box testing is testing where the developer will test every line of the program's code. To perform the white box testing, his/her aware of programming skills to design test cases.

Answer: (b) Low-level components are combined into clusters that perform a specific software sub-function.

Explanation: The Regression testing is used to authenticate a code change in the software, which does not impact the product's existing functionality. And it also ensures that the product works fine with new functionality, bug fixes, or any change in the existing feature.

Answer: (d) Smoke testing

Explanation: The smoke testing is used to test the basic and critical feature of an application before doing one round of deep, rigorous testing or checking all possible positive and negative values. In this testing, we do not require to design test cases.

Answer: (b) Non-existent loop termination

Explanation: The test case is specifying as a group of conditions under which a tester controls whether a software application is working as per the customer's requirements or not. And the test case provides us complete information about testing strategy, testing process, preconditions, and expected output.

Answer: (b) Black-box test design technique

Explanation: The Decision table technique is one of the most important used case design techniques for black-box testing. It is a systematic approach where several input combinations and their respective system behavior are captured in a tabular form. The Decision table technique is suitable for the functions, which have a logical relationship between two and more than two inputs.

Answer: (d) The risk is resolved.

Explanation: Once the application's functionality is stable, the risk is resolved, when the time is less, we test the necessary features, and when the essential feature itself is not working correctly, we can stop the testing.

Answer: (d) Bugs

Explanation: The Bug is the informal name of defects, which means that software or application is not working as per the requirement. The bug occurred when developers made any mistake or error while developing the product. And the bug had various names in different companies such as error, issues, problem, fault, mistake, etc.

Answer: (c) Error guessing

Explanation: Error guessing is a technique in which there is no specific method for identifying the error. It completely depends on the tester and type of experience in the previous testing involvements because it does not follow any method and guidelines. The error guessing technique deals with all possible errors that cannot be identified as informal testing.

Answer: (a) Checking that we are building the system right

Explanation: The entire V model executes in two-phase; the complete review process is done in the verification phase. We can say that the verification is used to check that we are building the system right.

Answer: (B) Software requirements specification

Explanation: SRS [Software Requirement Specifications] is a document where all the details are converted to the detail document, which can be understood by the developers and the test engineers.

Answer: (C) Determining the test approach.

Explanation: It is a detailed document, which describes software testing areas and activities. The test approach is used to define the application's flow while performing testing and for future reference.

Answer: (a) A black box testing technique appropriate to all levels of testing.

Explanation: The equivalence partitions are derived from the requirements and specifications of the software. It is a software testing technique in which input data is divided into partitions of valid and invalid values, and all partitions must exhibit the same behavior.

Answer: (c) Independent Test Group.

Explanation: The ITG (Independent Test Group) is where the third party solves any problem to create objectivity.

Answer: (b) Mutation testing

Explanation: Mutation testing is a fault-based testing technique where we insert errors purposely into a program (under test) to verify whether the existing test case can detect the error or not. In this testing, the program's mutant is created by making some modifications to the original program.

Answer: (a) Risk

Explanation: Risk is the challenge that we need to face to test the application in the current release, and if the assumptions fail, then the risks are involved, such as the effect for an application, release date becomes postponed.

Answer: (a) White box testing

Explanation: The component testing is based on an application's inner workings and revolves around internal structure testing. And the developer performs the white box/ component testing because the developer has the internal knowledge of the application.