Hello! Good Morning! How are you guys today?
So, as said before, note the Part II of the 66 Questions of Quality Assurance, from careerrider.com and thank you to Rohit Srivastava.
If you want to check the SOURCE of the text, just click here. But if you do want to help me and access the blog and reading my comments and everything, stay tune for the next episodes. 🙂 I try to break on small posts so it would be one huge post – I really don’t like big posts because sometimes people feel like “Oh, my, I do have to read ALL of it?” or maybe you only have a few minutes from lunch to read it and don’t want to start all over…. whatever.
It is also pretty interesting that most of the questions are related to a products than to Softwares, but I do believe that this is also important to know. Knowledge is never enough!
So, here we go! Enjoy!
66 Software Quality Assurance, QA interview questions and answers – Part II
QA interview questions and answers – contributed by Rohit Srivastava
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.
Q32. Describe Use Case Testing.
Use Case: A use case is a description of the process which is performed by the end user for a particular task. Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other. Use case is written by the user point of view.
Use case Testing: the use case testing uses this use case to evaluate the application. So that, the tester can examines all the functionalities of the application. Use case testing cover whole application, tester performs this testing in step by step process to complete one task.
Q33. What type of tests you perform on the web based application?
For web application we perform following time of test:
1. Functionality Testing.
2. Usability Testing.
3. Navigation Testing.
4. Configuration and Compatibility testing.
5. Reliability and Availability Testing.
6. Performance Testing.
7. Load and Stress Testing.
8. Security Testing
Q34. What is Gantt Chart?
A Gantt Chart is used to represent a project schedule that includes duration of individual tasks or phases, their dependencies and ordering.
- It displays the start and end points of each task and the percentage of completion of each task
- It allows the planner to assess the duration of a project, identify the resources needed, and lay out the order in which tasks need to be performed.
- It is useful in managing the dependencies between tasks.
- Using Gantt chart each team member can view the product development schedule.
Q35 How to find all the Bugs during first round of Testing?
There could be several reasons for not debugging the entire bug in the first round of testing process. Debugging the showstopper in the first or second build is almost impossible. A found defect can cover up the other defects in the application. The thread which leads to on defect could be redirected to another defect, as the tester find the bug and lock that bug in report and after fixing of those bugs new bugs may also arises. It is difficult to keep testing on a known defective application. That is the reason we cannot find all the bug in first run and also we cannot perform Exhaustive testing.
Q36 How can u prepares the Test Plan without SRS?
We can prepare a test plan directly without having SRS, When the Requirements and URD(User Requirement Document )are available to us. URD is very helpful to determine the requirement of the user. The SRS document only contains the requirement of the user, but tester can also determine the requirement form the product. Without having SRS document we cannot estimate the Testing effort and cost of testing if we do not have SRS. SRS tell us on which platform our software is going to be used and on basis of this we perform the test on the application. Some time end user want to know what type of testing we are going to execute on the application for this we can send our test plan to the client.
Q37. What is the purpose of test strategy?
We need Test Strategy for the following reason:
1. To have a signed, sealed, and delivered document, where the document contains details about the testing methodology, test plan, and test cases.
2. Test strategy document tells us how the software product will be tested.
3. Test strategy document helps to review the test plan with the project team members.
4. It describes the roles, responsibilities and the resources required for the test and schedule.
5. When we create a test strategy document, we have to put into writing any testing issues requiring resolution.
6. The test strategy is decided first, before lower level decisions are made on the test plan, test design, and other testing issues.
Q38. What are the dimensions of the Risks?
The dimensions of the risk are described below:
Schedule: Unrealistic schedules. to develop a huge software in a single day..
Client: Ambiguous requirements definition, requirement and not clear, changes in the requirement etc.
Human Resources: Non-availability of sufficient resources with the skill level expected in the project.
System Resources: Non-availability of procuring all critical computer resources either hardware and software tools or licenses for software will have an adverse impact.
Quality: Compound factors like lack of resources along with a tight delivery schedule and frequent changes to requirements will have an impact on the quality of the product tested.
Q39. How to Estimate Testing effort ?
Time Estimation method for Testing Process:
Step 1 : count number of use cases (NUC) of system
Step 2 : Set Avg. Time Test Cases(ATTC) as per test plan
Step 3 : Estimate total number of test cases (NTC)
Total number of test cases = Number of Use Cases X Avg. Test Cases per a use case
Step 4 : Set Avg. Execution Time (AET) per a test case
Step 5 : Calculate Total Execution Time (TET)
TET = Total number of test cases * AET
Step 6 : Calculate Test Case Creation Time (TCCT)
usually we will take 1.5 times of TET as TCCT
TCCT = 1.5 * TET
Step 7 : Time for Re-Test Case Execution (RTCE) this is for retesting
usually we take 0.5 times of TET
RTCE = 0.5 * TET
Step 8 : Set Report generation Time (RGT
usually we take 0.2 times of TET
RGT = 0.2 * TET
Step 9 : Set Test Environment Setup Time (TEST)
it also depends on test plan
Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer.
Q40. How to create requirements test matrix template?
For a requirements test matrix template we perform following step:
Step 1: Find out number of requirements.
Step 2: Find out number of test cases.
Step 3: Create a table based on these. Let we have 10 requirements and 40 test cases, then we create a table of 11 rows and 41 columns.
Step 4: On the first column of table copy all your 10 requirement numbers, and paste them into rows 2 through 11 of the table.
Step 5: Now copy all 40 test case numbers, and paste them into columns 2 through 41 of the table.
Step 6: Examine each of your 40 test cases, determine which of the 10 requirements they satisfy.
Q41. Can you perform regression testing performed manually?
Yes we can perform regression testing manually, but it requires lots of effort. To choose the way of doing the regression testing is totally depends on the initial testing approach. If the initial testing approach was manual testing, then the regression testing is usually performed manually. In case, if the initial testing approach was automated testing, then the regression testing is usually performed by automated testing. Automated regression testing is very easy task.
Q42. You are a tester. Now How will you choose which defect to remove in 1000000 defects?
First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs. These bugs are now reported in bug report template with the severity and priority of the bug. Tester assigns severity level to the defects depending upon their impact on other parts of application. Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible. We have 5 levels as:
Q43.How do you perform integration testing?
Integration testing is black box testing. Integration testing focuses on the interfaces between units, to make sure the units work together. For integration testing we ensure that all units testing of the each component is performed earlier. Integration testing begins only after the unit testing. The purpose of integration testing is to ensure different components of the application interact with each other. So that, components work as per the customer requirements. Test cases are developed with the purpose of exercising the interfaces between the components. Integration testing is considered complete, when actual results and expected results are same.
Q44. What is the testing lifecycle?
There is no standard testing life cycle, but it is consist of following phases:
- Test Planning (Test Strategy, Test Plan, Test Bed Creation)
- Test Development (Test Procedures, Test Scenarios, Test Cases)
- Test Execution
- Result Analysis (compare Expected to Actual results)
- Defect Tracking
Q45.What is good code?
A good code is code that works. The good code must not contain the defect or bug and is readable by other developers and easily maintainable. Organizations have coding standards all developers should follow, and also every programmer and software engineer has different ideas about what is best and what are too many or too few rules. We need to keep in mind that excessive use of rules can decrease both productivity and creativity. Peer reviews and code analysis tools can be used to check for problems and enforce standards.
Q46. What are the main attributes of test automation?
The main attributes are discussed below:
Maintainability: For each new release need to update the test automation suites.
Reliability: Accuracy and repeatability of the test automation.
Flexibility: Ease of working with all the different kinds of automation test ware.
Efficiency: Total cost related to the effort needed for the automation.
Portability: Ability of the automated test to run on different environments.
Robustness: Effectiveness of automation on an unstable or rapidly changing system.
Usability: Extent to which automation can be used by different types of user.
Q47. What could go wrong with test automation?
Followings things may be go wrong in test automation:
- Ignoring automation, while planning the development phases.
- In design Phase not choosing the right technology.
- In coding Phase not automating the right test cases.
- Tool selection might go wrong.
- Test script not be updated when application is continuously changing.
- Test data should be unique, if the same data is available on the application then the application will not accept the data that we are going to add via automation.
Q48. What tools are available to support testing during development of application?
Following tools can be used to support testing during development of application:
- Test management tools example: Quality Center, JIRA.
- Defect management tool example: Bugzilla, Test Director.
- Project management: Sharepoint.
- Automation tools: QTP, RFT, WinRunner.
Q49. What are the tests activities that you want to automate in a project?
The following testing activities can be automated:
- Functional tests: Identify some P1 and P2 cases which are most critical for project success and operations and automate them. After every new build, these scripts will assure the fixes does not broke any of the critical functionality.
- Regression test suites: Test the need to be run after each build.
- Performance tests: Identical test the need to be run on different browser.
- Stress tests
- Load tests
Q50. What is the difference in responsibilities of Programmers and QA analyst?
The differences in responsibilities are listed below:
- QA is concern for Process Quality and Programmers are concern for Product Quality.
- QA ensure that the processes used for developing the product of high quality where as programmers used these processes so that end product is of good quality.
- Processes are decided by QA. Programmers are supposed to follow the processes so that they can produce a good quality product.
- Any issue found during execution of process by the programmers is communicated to the QA so that they can improve the process.