Q21. What are test driver and test stub and why we need them?
- The Stub is called from the software component to be tested. It is used in top down approach.
- The driver calls a component to be tested. It is used in bottom up approach.
- Both test stub and test driver are dummy software components.
We need test stub and test driver because of following reason:
- Suppose we want to test the interface between modules A and B and we have developed only module A. So we cannot test module A but if a dummy module is prepare, using that we can test module A.
- Now module B cannot send or receive data from module A directly so, in these cases we have to transfer data from one module to another module by some external features. This external feature used is called Driver.
Q22. What is Monkey testing?
Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this tester enter the data in any format and check the software is not crashing. In this testing we use Smart monkey and Dumb monkey.
- Smart monkeys are used for load and stress testing, they will help in finding the bugs. They are very expensive to develop.
- Dumb monkey, they are important for basic testing. They help in finding those bugs which are having high severity. Dumb monkey are less expensive as compare to Smart monkeys.
Example: In phone number filed Symbols are entered.
Q23. What is Bug Triage?
Bug triage is a process to:
- Ensure bug report completeness.
- Analyze and assign bug to proper component.
- Assign bug to proper bug owner.
- Set appropriate bug priority.
- Adjust bug severity properly.
Q24. What is Traceability Matrix?
Traceability Matrix is a method used to validate the compliance of product with requirements for that product. The requirement is written in a row of the matrix and the columns of the matrix. Now they are used to identify how and where each requirement has been addressed.
It is in the form of table that correlates two base lined documents that require a many-to-many relationship. It is used with high level requirement and detailed requirement of the software product to the matching parts of high level design, detailed design, test plan, and test cases. The relationship to the source documents is required for both backward traceability and forward traceability.
Q26. Explain paradigms for interfacing module.
The paradigms for interfacing modules:
- Procedure Call Interface: A procedure from one module calls to procedure of another module. The caller can pass data to the called procedure while calling and also the called procedure can pass data to the caller while returning control back to the caller procedure.
- Shared Memory: When a block of memory is shared between two modules. The memory block may be allocated by one of the two modules or third module of the same application.
- Message Passing Interface: One module generates a message and sends the message to another module. It helps in building up the communication between different process or modules.
Q27. What are the factors responsible for the estimation of system integration test cycle and total integration time?
The number of system integration test cycle and total integration time are determined by the following parameters:
- Number of modules in the system.
- Relative complexity of the modules.
- Relative complexity of the interface between the modules.
- Number of modules needed to be clustered together in each test cycle.
- Whether the modules to be integrated have been adequately tested before.
- Turnaround time for each test-debug-fix cycle.
Q28. What are the things the tests ensure?
Test must ensure that:
- The number of parameters sent in a message agrees with the number of parameters expected to receive.
- The parameter order in the message match the order expected.
- The field sizes and data type match.
- When a message is generated from stored data prior to being sent, the message truly reflects the stored data.
- When a received message is stored, data copying is consistent with the received message.
Q29. What is random testing?
When test inputs are selected randomly from the input domain of the system, this is Random Testing. Random testing involve following procedure:
- The input domain is selected.
- Test inputs are selected independently from the domain.
- The system under test is executed on these inputs. The inputs constitute a random test set.
- The results are compared to the system specification. The test is a failure if any input leads to incorrect results, otherwise it is a success.
Q30. What are the benefits of Automated Testing?
The benefits of Automation Testing are below:
- Test engineer productivity.
- Coverage of regression testing.
- Reusability of test cases.
- Consistency in testing.
- Test interval reduction
- Reduced software maintenance cost
- Increased test effectiveness
Q31. What is Agile Testing?
Agile Testing means to quickly validation of the client requirements and make the application of good quality user interface. When the build is released to the testing team, testing of the application is started to find the bugs. As a Tester, we need to focus on the customer or end user requirements. We put the efforts to deliver the quality product in spite of short time frame which will further help in reducing the cost of development and test feedbacks will be implemented in the code which will avoid the defects coming from the end user.