ISTQB Advanced Test Manager Exam Preparation (Part 6)
Prior to appearing for exam for ISTQB certification, it is wise to quickly brush up your knowledge by reviewing the following testing related terms that are extremely important from examination point of view.
Part 6 of 12
Q. 51: What is Branch Decision Testing?
This test method uses a model of the source code which identifies individual decisions, and their outcomes. A �decision� is defined as being an executable statement containing its own logic.
This logic may also have the capability to transfer control to another statement. Each test case is designed to exercise the decision outcomes. In order to use this method, the input to each component must be identified.
<<<<<< =================== >>>>>>
Q. 52: What is Branch Condition Testing?
Branch Condition Testing uses a model of the source code, and identifies decisions based on individual Boolean operands within each decision condition. A �decision� is defined as being an executable statement containing its own logic.
An example of a decision would be a �loop� in a program.
<<<<<< =================== >>>>>>
Q. 53: What is Branch Condition Combination Testing?
Branch Condition Combination Testing uses a model of the source code, and identifies decisions based on combinations of Boolean operands within decision conditions. This logic may also have the capability to transfer control to another statement. The decision condition is a Boolean expression which is evaluated to determine the outcome of the decision.
<<<<<< =================== >>>>>>
Q. 54: What is Requirements Based Functional Testing?
Requirements-based Testing is simply testing the functionality of the software/system based on the requirements. The tests themselves should be derived from the documented requirements and not based on the software code itself. This method of functional testing ensures that the users will be getting what they want, as the requirements document basically specifies what the user has asked for.
<<<<<< =================== >>>>>>
Q. 55: What is Useability Testing?
This is where consideration is taken into account of how the user will use the product. It is common for considerable resources to be spent on defining exactly what the customer requires and how simple it is to use the program to achieve there aims. For example; test cases could be created based on the Graphical User Interface, to see how easy it would be to use in relation to a typical customer scenario.
<<<<<< =================== >>>>>>
Q. 56: What is Volume Testing?
Volume Testing is a form of Systems Testing. It primary focus is to concentrate on testing the systems while subjected to heavy volumes of data. Testing should be approached from a negative point of view to show that the program/system cannot operate correctly when using the volume of data specified in the requirements.
<<<<<< =================== >>>>>>
Q. 57: What is Performance Testing?
A program/system may have requirements to meet certain levels of performance. For a program, this could be the speed of which it can process a given task. For a networking device, it could mean the throughput of network traffic rate. Often, Performance Testing is designed to be negative, i.e. prove that the system does not meet its required level of performance.
<<<<<< =================== >>>>>>
Q. 58: What is Stress Testing?
Stress Testing simply means putting the system under stress. The testing is not normally carried out over a long period, as this would effectively be a form of duration testing. Imagine a system was designed to process a maximum of 1000 transactions in an hour. A stress test would be seeing if the systems could actually cope with that many transactions in a given time period. A useful test in this case would be to see how the system copes when asked to process more than 1000.
<<<<<< =================== >>>>>>
Q. 59: What is Dynamic Analysis?
Dynamic analysis is a testing method that can provide information on the state of software. It can achieve this dynamically i.e. it provides information when the software is actually running. It is commonly used to exercise parts of the program that use memory resources e.g.:
# Memory allocation
# Memory usage
# Memory de-allocation
# Memory leaks
# Unassigned pointers
<<<<<< =================== >>>>>>
Q. 60: What is Static Analysis?
Static Analysis is a set of methods designed to analyze software code in an effort to establish it is correct, prior to actually running the software. As we already know, the earlier we find a fault the cheaper it is to fix. So by using Static Analysis, we can effectively test the program even before it has been written. This would obviously only find a limited number of problems, but at least it is something that can be done very early on in the development lifecycle.
Part -7 of Key Fundamental Terms
Full Study Material for ISTQB Advanced Test Manager Exam
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.