|1 Crore+ students have signed up on EduRev. Have you?|
1. What are the different Ways of doing Black Box testing?
There are five methodologies most frequently used:
2. Can you explain TPA analysis?
TPA is a technique used to estimate test efforts for black box testing. Inputs for TPA are the counts derived from function points.
Below are the features of TPA:
3. Can you explain the elementary process?
Software applications are a combination of elementary processes. When elementary processes come together they form a software application.
There are two types of elementary processes:
1.Dynamic elementary Process: The dynamic elementary process moves data from an internal application boundary to an external application boundary or vice-versa. Example: Input data screen where a user inputs data into the application. Data moves from the input screen inside the application.
2.Static elementary Process: Static elementary process which maintains the data of the application either inside the application boundary or in the external application boundary. For example, in a customer maintenance screen maintaining customer data is a static elementary process.
4. How do you estimate white box testing?
The testing estimates derived from function points are actually the estimates for white box testing. So in the following figure the man days are actually the estimates for white box testing of the project. It does not take into account black box testing estimation.
5. Can you explain the various elements of function points FTR, ILF, EIF, EI, EO, EQ, and GSC?
6. Can you explain an Application boundary?
The first step in FPA is to define the boundary. There are two types of major boundaries:
The external application boundary can be identified using the following litmus test:
7. Can you explain how TPA works?
There are three main elements which determine estimates for black box testing: size, test strategy, and productivity. Using all three elements we can determine the estimate for black box testing for a given project. Let's take a look at these elements.
2.Interfacing: How much does one function affect the other part of the system? If a function is modified then accordingly the other systems have to be tested as one function always impacts another.
3.Uniformity: How reusable is the application? It is important to consider how many similar structured functions exist in the system. It is important to consider the extent to which the system allows testing with slight modifications.
2.Test strategy: Every project has certain requirements. The importance of all these requirements also affects testing estimates. Any requirement importance is from two perspectives: one is the user importance and the other is the user usage. Depending on these two characteristics a requirement rating can be generated and a strategy can be chalked out accordingly, which also means that estimates vary accordingly.
3.Productivity: This is one more important aspect to be considered while estimating black box testing. Productivity depends on many aspects.
8. Can you explain steps in function points?
Below are the steps in function points:
9. Can you explain function points?
Function points are a unit measure for software much like an hour is to measuring time, miles are to measuring distance or Celsius is to measuring temperature. Function Points are an ordinal measure much like other measures such as kilometers, Fahrenheit, hours, so on and so forth.
This approach computes the total function points (FP) value for the project, by totaling the number of external user inputs, inquiries, outputs, and master files, and then applying the following weights: inputs (4), outputs (5), inquiries (4), and master files (10). Each FP contributor can be adjusted within a range of +/-35% for a specific project complexity.