Given the following types of tool, which tools would typically be used by developers, and which by an independent system test team? Which of the following is likely to benefit most from the use of test tools providing test capture and replay facilities? A deviation from the specified or expected behavior that is visible to end-users is called: a an error b a fault c a failure d a defect Ans: C 2.
A configuration management system would NOT normally provide: a Linkage of customer requirements to version numbers. Test cases are designed during: a Test recording.
Which of the following statements about reviews is true? Ans: A 5. Ans: A 7. Which of the following is not a type of incremental testing approach? Pick the best definition of quality a Quality is job one b Zero defects c Work as designed d Conformance to requirements Ans: D Fault Masking is a Creating a test case which does not reveal a fault b Error condition hiding another error condition c Masking a fault by developer d Masking a fault by a tester Ans: B Boundary value testing a Is the same as equivalence partitioning tests b Tests combinations of input circumstances c Test boundary conditions on, below and above the edges of input and output equivalence classes d Is used in white box testing strategy Ans: C In a review meeting a moderator is a person who: a Takes minutes of the meeting b Takes telephone calls c Mediates between people d writes the documents to be reviewed Ans: C How much testing is enough?
Ans: D Which of the following is false? Objective Questions on Software Testing 1. Which of the following is the odd one out? Which of the following is a static test? Which of the following is a black box design technique? Which of the following is not the integration strategy?
Which of the following is NOT a reasonable test objective: a To find faults in the software b To give confidence in the software c To prove that the software has no faults d To find performance problems Ans: C 6. Which of the following uses Impact Analysis most?
Traceability Matrix : Mapping between test cases and customer requirements is known as Traceability Matrix. Both stubs and drivers are part of incremental testing. In incremental testing, there are two approaches namely bottom-up and top-down approach. Drivers are used in bottom-up testing and stub is used for a top-down approach.
In order to test the main module, the stub is used, which is a dummy code or program. The key words control the processing. It is also used for the visualization of data processing. The cycle is repeated unless there are no errors found. Fuzz testing is used to detect security loopholes and coding errors in software.
In this technique, random data is added to the system in an attempt to crash the system. If vulnerability persists, a tool called fuzz tester is used to determine potential causes. This technique is more useful for bigger projects but only detects a major fault. None of the characters should get truncated. Junk characters should not be added. The code coverage testing tool runs parallel while performing testing on the actual product. The code coverage tool monitors the executed statements of the source code.
When the final testing is done, we get a complete report of the pending statements and also get the coverage percentage. In simple terms when a defect reaches the end customer, it is called a failure while the defect is identified internally and resolved; then it is referred to as a defect. Black box test cases are written first as to write black box test cases; it requires project plan and requirement document all these documents are easily available at the beginning of the project.
While writing white box test cases requires more architectural understanding and is not available at the start of the project. Bottom-up testing is an approach to integration testing, where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.
Breath testing is a test suite that exercises the full functionality of a product but does not test features in detail. Code Walk Through is the informal analysis of the program source code to find defects and verify coding techniques. End-to-end testing is done after functional testing.
The purpose behind doing end-to-end testing is that. A test harness is configuring a set of tools and test data to test an application in various conditions, and it involves monitoring the output with expected output for correctness.
Risk-based Testing is the term used for an approach to creating a Test Strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.
Preventative tests are designed early; reactive tests are designed after the software has been produced. Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations.
In a decision table, the inputs are listed in a column, with the outputs in the same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced. The techniques of equivalence partitioning and boundary value analysis are often applied to specific situations or inputs.
However, if different combinations of inputs result in different actions being taken, this can be more difficult to show using equivalence partitioning and boundary value analysis, which tend to be more focused on the user interface. The other two specification-based techniques, decision tables, and state transition testing are more focused on business logic or business rules.
A decision table is a good way to deal with combinations of things e. The difference between a pilot and beta testing is that pilot testing is actually done using the product by the group of users before the final deployment, and in beta testing, we do not input real data, but it is installed at the end customer to validate if the product can be used in production.
Testing technique: — Is a process for ensuring that some aspects of the application system or unit functions properly there may be few techniques but many tools. Testing Tools: — Is a vehicle for performing a test process.
The tool is a resource to the tester, but itself is insufficient to conduct testing. Learn More About Testing Tools here. Component testing, also known as unit, module, and program testing, searches for defects in and verifies the functioning of software e. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system.
Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components simply. A stub is called from the software component to be tested; a driver calls a component to be tested. Here is an awesome video on Unit Testing. Testing the end to end functionality of the system as a whole is defined as a functional system testing.
Random testing is often known as monkey testing. In such type of testing data is generated randomly often using a tool or automated mechanism. With this randomly generated input, the system is tested, and results are analyzed accordingly.
These testing are less reliable; hence it is normally used by the beginners and to see whether the system will hold up under adverse effects. In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps:. The moderator or review leader leads the review process. He or she determines, in co-operation with the author, the type of review, approach and the composition of the review team. The moderator performs the entry check and the follow-up on the rework, in order to control the quality of the input and output of the review process.
The moderator also schedules the meeting, disseminates documents before the meeting, coaches other team members, paces the meeting, leads possible discussions and stores the data that is collected. Learn More about Review process in Video Tutorial here. Structure-based testing techniques which are also dynamic rather than static use the internal structure of the software to derive test cases.
For example, a structural technique may be concerned with exercising loops in the software. Different test cases may be derived to exercise the loop once, twice, and many times. This may be done regardless of the functionality of the software. After the software has changed or when the environment has changed Regression testing should be performed.
A negative test is when you put in an invalid input and receives errors. While positive testing is when you put in a valid input and expect some action to be completed in accordance with the specification. Re-testing ensures the original fault has been removed; regression testing looks for unexpected side effects.
The experience of both technical and business people is important, as they bring different perspectives to the test analysis and design process.
Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing. It depends on the risks for the system being tested.
There are some criteria based on which you can stop testing. The primary purpose of the integration strategy is to specify which modules to combine when and how many at once. Semi-random test cases are nothing, but when we perform random test cases and do equivalence partitioning to those test cases, it removes redundant test cases, thus giving us semi-random test cases.
Regression testing should be done on other modules as well because fixing one module may affect other modules. Because configuration management assures that we know the exact version of the testware and the test object. A software development model that illustrates how testing activities integrate with software development phases.
Test coverage measures in some specific way the amount of testing performed by a set of tests derived in some other way, e. Wherever we can count things and can tell whether or not each of those things has been tested by some test, then we can measure coverage.
0コメント