Software Testing Interview Questions and Answers
by sonia, on May 26, 2017 3:36:46 PM
Q1. What is the MAIN benefit of designing tests early in the life cycle?
Ans: It helps prevent defects from being introduced into the code.
Q2. What is risk-based testing?
Ans: 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.
Q3. A wholesaler sells printer cartridges. The minimum order quantity is 5. There is a 20% discount for orders of 100 or more printer cartridges. You have been asked to prepare test cases using various values for the number of printer cartridges ordered. Which of the following groups contain three test inputs that would be generated using Boundary Value Analysis?
Ans: 4, 5, 99
Q4. What is the KEY difference between preventative and reactive approaches to testing?
Ans: Preventative tests are designed early; reactive tests are designed after the software has been produced.
Q5. What is the purpose of exit criteria?
Ans: The purpose of exit criteria is to define when a test level is completed.
Q6. What determines the level of risk?
Ans: The likelihood of an adverse event and the impact of the event determine the level of risk.
Q7. When is used Decision table testing?
Ans: 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.
Learn More About Decision Table Testing Technique in the Video Tutorial here
Q8. What is the MAIN objective when reviewing a software deliverable?
Ans: To identify defects in any software work product.
Q9. Which of the following defines the expected results of a test? Test case specification or test design specification.
Ans: Test case specification defines the expected results of a test.
Q10. What is the benefit of test independence?
Ans: It avoids author bias in defining effective tests.
Q11. As part of which test process do you determine the exit criteria?
Ans: The exit criteria is determined on the bases of 'Test Planning'.
Q12. What is beta testing?
Ans: Testing performed by potential customers at their own locations.
Q13. Given the following fragment of code, how many tests are required for 100% decision coverage?
if width > length
thenbiggest_dimension = width
if height > width
thenbiggest_dimension = height
elsebiggest_dimension = length
if height > length
thenbiggest_dimension = height
Q14. You have designed test cases to provide 100% statement and 100% decision coverage for the following fragment of code. if width > length then biggest_dimension = width else biggest_dimension = length end_if The following has been added to the bottom of the code fragment above. print "Biggest dimension is " &biggest_dimensionprint "Width: " & width print "Length: " & length How many more test cases are required?
Ans: None, existing test cases can be used.
Q15. Rapid Application Development?
Ans: Rapid Application Development (RAD) is formally a parallel development of functions and subsequent integration. Components/functions are developed in parallel as if they were mini projects, the developments are time-boxed, delivered, and then assembled into a working prototype. This can very quickly give the customer something to see and use and to provide feedback regarding the delivery and their requirements. Rapid change and development of the product is possible using this methodology. However the product specification will need to be developed for the product at some point, and the project will need to be placed under more formal controls prior to going into production.
Q16. What is the difference between Testing Techniques and Testing Tools?
Ans: 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
Q17. We use the output of the requirement analysis, the requirement specification as the input for writing …
Ans: User Acceptance Test Cases
Q18. Repeated Testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component:
Ans: Regression Testing
Q19. What is component testing?
Ans: Component testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are separately testable. 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 in a simple manner. A stub is called from the software component to be tested; a driver calls a component to be tested.
Q20. What is functional system testing?
Ans: Testing the end to end functionality of the system as a whole is defined as a functional system testing.
Q21. What are the benefits of Independent Testing?
Ans: Independent testers are unbiased and identify different defects at the same time.
Q22. In a REACTIVE approach to testing when would you expect the bulk of the test design work to be begun?
Ans: The bulk of the test design work begun after the software or system has been produced.
Q23. What are the different Methodologies in Agile Development Model?
Ans: There are currently seven different agile methodologies that I am aware of:
- Extreme Programming (XP)
- Lean Software Development
- Feature-Driven Development
- Agile Unified Process
- Dynamic Systems Development Model (DSDM)
Q24. Which activity in the fundamental test process includes evaluation of the testability of the requirements and system?
Ans: A 'Test Analysis' and 'Design' includes evaluation of the testability of the requirements and system.
Q25. What is typically the MOST important reason to use risk to drive testing efforts?
Ans: Because testing everything is not feasible.
Q26. What is random/monkey testing? When it is used?
Ans: Random testing 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 analysed 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.
Q27. Which of the following are valid objectives for incident reports?
- Provide developers and other parties with feedback about the problem to enable identification, isolation and correction as necessary.
- Provide ideas for test process improvement.
- Provide a vehicle for assessing tester competence.
- Provide testers with a means of tracking the quality of the system under test.
Q28. Consider the following techniques. Which are static and which are dynamic techniques?
- Equivalence Partitioning.
- Use Case Testing.
- Data Flow Analysis.
- Exploratory Testing.
- Decision Testing.
Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use Case Testing, Exploratory Testing and Decision Testing are dynamic.
Q29. Why are static testing and dynamic testing described as complementary?
Ans: Because they share the aim of identifying defects but differ in the types of defect they find.
Q30. What are the phases of a formal review?
Ans: In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps:
- Review meeting
Q31. What is the role of moderator in review process?
Ans: 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.
Q32. What is an equivalence partition (also known as an equivalence class)?
Ans: An input or output ranges of values such that only one value in the range becomes a test case.
Q33. When should configuration management procedures be implemented?
Ans: During test planning.
Q34. A Type of functional Testing, which investigates the functions relating to detection of threats, such as virus from malicious outsiders?
Ans: Security Testing
Q35. Testing where in we subject the target of the test , to varying workloads to measure and evaluate the performance behaviours and ability of the target and of the test to continue to function properly under these different workloads?
Ans: Load Testing
Q36. Testing activity which is performed to expose defects in the interfaces and in the interaction between integrated components is?
Ans: Integration Level Testing
Q37. What are the Structure-based (white-box) testing techniques?
Ans: Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software is implemented, that is, how it works. 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.
Q38. When "Regression Testing" should be performed?
Ans: After the software has changed or when the environment has changed Regression testing should be performed.
Q39. What is negative and positive testing?
Ans: A negative test is when you put in an invalid input and receives errors. While a positive testing, is when you put in a valid input and expect some action to be completed in accordance with the specification.
Q40. What is the purpose of a test completion criterion?
Ans: The purpose of test completion criterion is to determine when to stop testing
Q41. What can static analysis NOT find?
Ans: For example memory leaks.
Q42. What is the difference between re-testing and regression testing?
Ans: Re-testing ensures the original fault has been removed; regression testing looks for unexpected side effects.
Q43. What are the Experience-based testing techniques?
Ans: In experience-based techniques, people's knowledge, skills and background are a prime contributor to the test conditions and test cases. 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.
Q44. What type of review requires formal entry and exit criteria, including metrics?
Q45. Could reviews or inspections be considered part of testing?
Ans: Yes, because both help detect faults and improve quality.
Q46. An input field takes the year of birth between 1900 and 2004 what are the boundary values for testing this field?
Q47. Which of the following tools would be involved in the automation of regression test?
- Data tester
- Boundary tester
- Output comparator.
Ans: d. Output comparator
Q48. To test a function, what has to write a programmer, which calls the function to be tested and passes it test data.
Q49. What is the one Key reason why developers have difficulty testing their own work?
Ans: Lack of Objectivity
Q50."How much testing is enough?"
Ans: The answer depends on the risk for your industry, contract and special requirements.
Q51. When should testing be stopped?
Ans: It depends on the risks for the system being tested. There are some criteria bases on which you can stop testing.
- Deadlines (Testing, Release)
- Test budget has been depleted
- Bug rate fall below certain level
- Test cases completed with certain percentage passed
- Alpha or beta periods for testing ends
- Coverage of code, functionality or requirements are met to a specified point
Q52. Which of the following is the main purpose of the integration strategy for integration testing in the small?
Ans: The main purpose of the integration strategy is to specify which modules to combine when and how many at once.
Q53. What are semi-random test cases?
Ans: 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.
Q54. Given the following code, which statement is true about the minimum number of test cases required for full statement and branch coverage?
IF p+q> 100
THEN Print "Large"
IF p > 50
THEN Print "p Large"
Ans: 1 test for statement coverage, 2 for branch coverage
Q55. What is black box testing? What are the different black box testing techniques?
Ans: Black box testing is the software testing method which is used to test the software without knowing the internal structure of code or program. This testing is usually done to check the functionality of an application. The different black box testing techniques are
- Equivalence Partitioning
- Boundary value analysis
- Cause effect graphing
Q56. Which review is normally used to evaluate a product to determine its suitability for intended use and to identify discrepancies?
Ans: Technical Review.
Q57. Why we use decision tables?
Ans: 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.g. inputs). This technique is sometimes also referred to as a 'cause-effect' table. The reason for this is that there is an associated logic diagramming technique called 'cause-effect graphing' which was sometimes used to help derive the decision table
Q58. Faults found should be originally documented by whom?
Ans: By testers.
Q59. Which is the current formal world-wide recognized documentation standard?
Ans: There isn't one.
Q60. Which of the following is the review participant who has created the item to be reviewed?
Q61. A number of critical bugs are fixed in software. All the bugs are in one module, related to reports. The test manager decides to do regression testing only on the reports module.
Ans: Regression testing should be done on other modules as well because fixing one module may affect other modules.
Q62. Why does the boundary value analysis provide good test cases?
Ans: Because errors are frequently made during programming of the different cases near the 'edges' of the range of values.
Q63. What makes an inspection different from other review types?
Ans: It is led by a trained leader, uses formal entry and exit criteria and checklists.
Q64. Why can be tester dependent on configuration management?
Ans: Because configuration management assures that we know the exact version of the testware and the test object.
Q65. What is a V-Model?
Ans: A software development model that illustrates how testing activities integrate with software development phases
Q66. What is maintenance testing?
Ans: Triggered by modifications, migration or retirement of existing software
Q67. What is test coverage?
Ans: Test coverage measures in some specific way the amount of testing performed by a set of tests (derived in some other way, e.g. using specification-based techniques). 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.
Q68. Why is incremental integration preferred over "big bang" integration?
Ans: Because incremental integration has better early defects screening and isolation ability
Q69. When do we prepare RTM (Requirement traceability matrix), is it before test case designing or after test case designing?
Ans: It would be before test case designing. Requirements should already be traceable from Review activities since you should have traceability in the Test Plan already. This question also would depend on the organisation. If the organisations do test after development started then requirements must be already traceable to their source. To make life simpler use a tool to manage requirements.
Q70. What is called the process starting with the terminal modules?
Ans: Bottom-up integration
Q71. During which test activity could faults be found most cost effectively?
Ans: During test planning
Q72. The purpose of requirement phase is
Ans: To freeze requirements, to understand user needs, to define the scope of testing
Q73. Why we split testing into distinct stages?
Ans: We split testing into distinct stages because of following reasons,
- Each test stage has a different purpose
- It is easier to manage testing in stages
- We can run different test into different environments
- Performance and quality of the testing is improved using phased testing
Q74. What is DRE?
Ans: To measure test effectiveness a powerful metric is used to measure test effectiveness known as DRE (Defect Removal Efficiency) From this metric we would know how many bugs we have found from the set of test cases. Formula for calculating DRE is
DRE=Number of bugs while testing / number of bugs while testing + number of bugs found by user
Q75. Which of the following is likely to benefit most from the use of test tools providing test capture and replay facilities? a) Regression testing b) Integration testing c) System testing d) User acceptance testing
Ans: Regression testing
Q76. How would you estimate the amount of re-testing likely to be required?
Ans: Metrics from previous similar projects and discussions with the development team
Q77. What studies data flow analysis?
Ans: The use of data on paths through the code.
Q78. What is Alpha testing?
Ans: Pre-release testing by end user representatives at the developer's site.
Q79. What is a failure?
Ans: Failure is a departure from specified behaviour.
Q80. What are Test comparators?
Ans: Is it really a test if you put some inputs into some software, but never look to see whether the software produces the correct result? The essence of testing is to check whether the software produces the correct result, and to do that, we must compare what the software produces to what it should produce. A test comparator helps to automate aspects of that comparison.
Q81. Who is responsible for document all the issues, problems and open point that were identified during the review meeting
Q82. What is the main purpose of Informal review
Ans: Inexpensive way to get some benefit
Q83. What is the purpose of test design technique?
Ans: Identifying test conditions and Identifying test cases
Q84. When testing a grade calculation system, a tester determines that all scores from 90 to 100 will yield a grade of A, but scores below 90 will not. This analysis is known as:
Ans: Equivalence partitioning
Q85. A test manager wants to use the resources available for the automated testing of a web application?
Ans: The best choice is Tester, test automater, web specialist, DBA
Q86. During the testing of a module tester 'X' finds a bug and assigned it to developer. But developer rejects the same, saying that it's not a bug. What 'X' should do?
Ans: Send to the detailed information of the bug encountered and check the reproducibility
Q87. A type of integration testing in which software elements, hardware elements, or both are combined all at once into a component or an overall system, rather than in stages.
Ans: Big-Bang Testing
Q88). In practice, which Life Cycle model may have more, fewer or different levels of development and testing, depending on the project and the software product. For example, there may be component integration testing after component testing, and system integration testing after system testing.
Q89. Which technique can be used to achieve input and output coverage? It can be applied to human input, input via interfaces to a system, or interface parameters in integration testing.
Ans: Equivalence partitioning
Q90. "This life cycle model is basically driven by schedule and budget risks" This statement is best suited for…
Q91. In which order should tests be run?
Ans: The most important one must tests first
Q92. The later in the development life cycle a fault is discovered, the more expensive it is to fix. Why?
Ans: The fault has been built into more documentation, code, tests, etc
Q93. What is Coverage measurement?
Ans: It is a partial measure of test thoroughness.
Q94. What is Boundary value testing?
Ans: Test boundary conditions on, below and above the edges of input and output equivalence classes. For instance, let say a bank application where you can withdraw maximum Rs.20,000 and a minimum of Rs.100, so in boundary value testing we test only the exact boundaries, rather than hitting in the middle. That means we test above the maximum limit and below the minimum limit.
Q95. What is Fault Masking?
Ans: Error condition hiding another error condition.
Q96. What does COTS represent?
Ans: Commercial off The Shelf.
Q97.The purpose of which is allow specific tests to be carried out on a system or network that resembles as closely as possible the environment where the item under test will be used upon release?
Ans: Test Environment
Q98. What can be thought of as being based on the project plan, but with greater amounts of detail?
Ans: Phase Test Plan
Q99. What is exploratory testing?
Ans: Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. For example, the tester may decide to use boundary value analysis but will think through and test the most important boundary values without necessarily writing them down. Some notes will be written during the exploratory-testing session, so that a report can be produced afterwards.
Q100. What is "use case testing"?
Ans: In order to identify and execute the functional requirement of an application from start to finish "use case" is used and the techniques used to do this is known as "Use Case Testing"
Q101. What is the difference between STLC (Software Testing Life Cycle) and SDLC (Software Development Life Cycle) ?
Ans: SDLC deals with developement/coding of the software while STLC deales with validation and verification of the software
Q102. What is traceability matrix?
Ans: The relationship between test cases and requirements is shown with the help of a document. This document is known as traceability matrix.
Q103. What is Equivalence partitioning testing?
Ans: Equivalence partitioning testing is a software testing technique which divides the application input test data into each partition at least once of equivalent data from which test cases can be derived. By this testing method it reduces the time required for software testing.
Q104. What is white box testing and list the types of white box testing?
Ans: White box testing technique involves selection of test cases based on an analysis of the internal structure (Code coverage, branches coverage, paths coverage, condition coverage etc.) of a component or system. It is also known as Code-Based testing or Structural testing. Different types of white box testing are
- Statement Coverage
- Decision Coverage
Q105. In white box testing what do you verify?
Ans: In white box testing following steps are verified.
- Verify the security holes in the code
- Verify the incomplete or broken paths in the code
- Verify the flow of structure according to the document specification
- Verify the expected outputs
- Verify all conditional loops in the code to check the complete functionality of the application
- Verify the line by line coding and cover 100% testing
Q106. What is the difference between static and dynamic testing?
Ans: Static testing: During Static testing method, the code is not executed and it is performed using the software documentation.
Dynamic testing: To perform this testing the code is required to be in an executable form.
Q107. What is verification and validation?
Ans: Verification is a process of evaluating software at development phase and to decide whether the product of a given application satisfies the specified requirements. Validation is the process of evaluating software at the end of the development process and to check whether it meets the customer requirements.
Q108. What are different test levels?
Ans: There are four test levels
- Unit/component/program/module testing
- Integration testing
- System testing
- Acceptance testing
Q109. What is Integration testing?
Ans: Integration testing is a level of software testing process, where individual units of an application are combined and tested. It is usually performed after unit and functional testing.
Q110. What are the tables in testplans?
Ans: Test design, scope, test strategies , approach are various details that Test plan document consists of.
- Test case identifier
- Features to be tested
- Features not to be tested
- Test strategy & Test approach
- Test deliverables
- Staffing and training
- Risk and Contingencies
Q111. What is the difference between UAT (User Acceptance Testing) and System testing?
Ans: System Testing: System testing is finding defects when the system under goes testing as a whole, it is also known as end to end testing. In such type of testing, the application undergoes from beginning till the end.
UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests which determines whether the product will meet the needs of its users.
Q112. Mention the difference between Data Driven Testing and Retesting?
Ans: Retesting: It is a process of checking bugs that are actioned by development team to verify that they are actually fixed.
Data Driven Testing (DDT): In data driven testing process, application is tested with multiple test data. Application is tested with different set of values.
Q113. What are the valuable steps to resolve issues while testing?
- Record : Log and handle any problems which has happened
- Report: Report the issues to higher level manager
- Control: Define the issue management process
Q114. What is the difference between test scenarios, test cases and test script?
Ans: Difference between test scenarios and test cases is that
Test Scenarios: Test scenario is prepared before the actual testing starts, it includes plans for testing product, number of team members, environmental condition, making test cases, making test plans and all the features that are to be tested for the product.
Test Cases: It is a document that contains the steps that has to be executed, it has been planned earlier.
Test Script: It is written in a programming language and it's a short program used to test part of functionality of the software system. In other words a written set of steps that should be performed manually.
Q115. What is Latent defect?
Ans: Latent defect: This defect is an existing defect in the system which does not cause any failure as the exact set of conditions has never been met
Q116. What are the two parameters which can be useful to know the quality of test execution?
Ans: To know the quality of test execution we can use two parameters
- Defect reject ratio
- Defect leakage ratio
Q117. What is the function of software testing tool "phantom"?
Ans: Phantom is a freeware, and is used for windows GUI automation scripting language. It allows to take control of windows and functions automatically. It can simulate any combination of key strokes and mouse clicks as well as menus, lists and more.
Q118. Explain what is Test Deliverables ?
Ans: Test Deliverables are set of documents, tools and other components that has to be developed and maintained in support of testing.
There are different test deliverables at every phase of the software development lifecycle
- Before Testing
- During Testing
- After the Testing
Q119. What is mutation testing?
Ans: Mutation testing is a technique to identify if a set of test data or test case is useful by intentionally introducing various code changes (bugs) and retesting with original test data/ cases to determine if the bugs are detected.
Q120. What all things you should consider before selecting automation tools for the AUT?
- Technical Feasibility
- Complexity level
- Application stability
- Test data
- Application size
- Re-usability of automated scripts
- Execution across environment
Q121. How will you conduct Risk Analysis?
Ans: For the risk analysis following steps need to be implemented
- Finding the score of the risk
- Making a profile for the risk
- Changing the risk properties
- Deploy the resources of that test risk
- Making a database of risk
Q122. What are the categories of debugging?
Ans: Categories for debugging
- Brute force debugging
- Cause elimination
- Program slicing
- Fault tree analysis
Q123. What is fault masking explain with example?
Ans: When presence of one defect hides the presence of another defect in the system is known as fault masking.
Example : If the "Negative Value" cause a firing of unhandled system exception, the developer will prevent the negative values inpu. This will resolve the issue and hide the defect of unhandled exception firing.
Q124. Explain what is Test Plan ? What are the information that should be covered in Test Plan ?
Ans: A test plan can be defined as a document describing the scope, approach, resources and schedule of testing activities and a test plan should cover the following details.
- Test Strategy
- Test Objective
- Exit/Suspension Criteria
- Resource Planning
- Test Deliverables
Q125. How you can eliminate the product risk in your project ?
Ans: To eliminate product risk in your project, there is simple yet crucial step that can reduce the product risk in your project.
- Investigate the specification documents
- Have discussions about the project with all stakeholders including the developer
- As a real user walk around the website
Q126. What are the common risk that leads to the project failure?
Ans: The common risk that leads to a project failure are
- Not having enough human resource
- Testing Environment may not be set up properly
- Limited Budget
- Time Limitations
Q127. On what basis you can arrive to an estimation for your project?
Ans: To estimate your project , you have to consider following points
- Divide the whole project into a smallest tasks
- Allocate each task to team members
- Estimate the effort required to complete each task
- Validate the estimation
Q128. Explain how you would allocate task to team members ?
Q129. Explain what is testing type and what are the commonly used testing type ?
Ans: To get an expected test outcome a standard procedure is followed which is referred as Testing Type.
Commonly used testing types are
- Unit Testing: Test the smallest code of an application
- API Testing: Testing API created for the application
- Integration Testing: Individual software modules are combined and tested
- System Testing: Complete testing of system
- Install/UnInstall Testing: Testing done from the point of client/customer view
- Agile Testing: Testing through Agile technique
Q130. While monitoring your project what all things you have to consider ?
Ans: The things that has to be taken in considerations are
- Is you project on schedule
- Are you over budget
- Are you working towards the same career goal
- Have you got enough resources
- Are there any warning signs of impending problems
- Is there any pressure from management to complete the project sooner
Q131. What are the common mistakes which creates issues ?
- Matching resources to wrong projects
- Test manager lack of skills
- Not listening to others
- Poor Scheduling
- Ignoring the small problems
- Not following the process
Q132. What does a typical test report contains? What are the benefits of test reports?
Ans: A test report contains following things:
- Project Information
- Test Objective
- Test Summary
The benefits of test reports are:
- Current status of project and quality of product are informed
- If required, stake holder and customer can take corrective action
- A final document helps to decide whether the product is ready for release
Q133. What is test management review and why it is important?
Ans: Management review is also referred as Software Quality Assurance or SQA. SQA focusses more on the software process rather than the software work products. It is a set of activities designed to make sure that the project manager follows the standard process. SQA helps test manager to benchmark the project against the set standards.
Q134. What are the best practices for software quality assurance?
Ans: The best practices for an effective SQA implementation is
- Continuous Improvement
- Tool Usage
- Responsibility by team members
- Experienced SQA auditors
Q135. When is RTM (Requirement Traceability Matrix) prepared ?
Ans: RTM is prepared before test case designing. Requirements should be traceable from review activities.
Q136. What is difference between Test matrix and Traceability matrix?
Ans: Test Matrix: Test matrix is used to capture actual quality, effort, the plan, resources and time required to capture all phases of software testing
Traceability Matrix:Mapping between test cases and customer requirements is known as Traceability Matrix
Q137. In manual testing what are stubs and drivers?
Ans: 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 top down approach. In order to test the main module, stub is used, whuich is a dummy code or program .
Q138. What are the step you would follow once you find the defect?
Ans: Once defect is found you would follow the step
- Recreate the defect
- Attach the screen shot
- Log the defect
Q139. Explain what is "Test Plan Driven" or "Key Word Driven" method of testing?
Ans: This technique uses the actual test case document developed by testers using a spread sheet containing special "key Words". The key words control the processing.
Q140. What is DFD (Data Flow Diagram) ?
Ans: When a "flow of data" through an information system is graphically represented then it is known as Data Flow Diagram. It is also used for the visualization of data processing.
Q141. Explain what is LCSAJ?
Ans: LCSAJ stands for 'linear code sequence and jump'. It consists of the following three items
- Start of the linear sequence of executable statements
- End of the linear sequence
- The target line to which control flow is transferred at the end of the linear sequence
Q142. Explain what is N+1 testing?
Ans: The variation of regression testing is represented as N+1. In this technique the testing is performed in multiple cycles in which errors found in test cycle 'N' are resolved and re-tested in test cycle N+1. The cycle is repeated unless there are no errors found.
Q143. What is Fuzz testing and when it is used?
Ans: Fuzz testing is used to detect security loopholes and coding errors in software. In this technique random data is added to the system in 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 major fault.
Q144. Mention what are the main advantages of statement coverage metric of software testing?
Ans: The benefit of statement coverage metric is that
- It does not require processing source code and can be applied directly to object code
- Bugs are distributed evenly through code, due to which percentage of executable statements covered reflects the percentage of faults discovered
Q145. How to generate test cases for replace string method?
- If characters in new string > characters in previous string. None of the characters should get truncated
- If characters in new string< characters in previous string. Junk characters should not be added
- Spaces after and before the string should not be deleted
- String should be replaced only for the first occurrence of the string
Q146. How will you handle a conflict amogst your team members ?
- I will talk individually to each person and note their concerns
- I will find solution to the common problems raised by team members
- I will hold a team meeting , reveal the solution and ask people to co-operate
Q147. Mention what are the categories of defects?
Mainly there are three defect categories
- Wrong: When requirement is implemented incorrectly
- Missing: It is a variance from the specification, an indication that a specification was not implemented or a requirement of the customer is not met
- Extra: A requirement incorporated into the product that was not given by the end customer. It is considered as a defect because it is a variance from the existing requirements
Q148. Explain how does a test coverage tool works?
Ans: 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.
Q149. Mention what is the difference between a "defect" and a "failure" in software testing?
Ans: 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 as defect.
Q150. Explain how to test documents in a project that span across the software development lifecycle?
Ans: The project span across the software development lifecycle in following manner
- Central/Project test plan: It is the main test plan that outlines the complete test strategy of the project. This plan is used till the end of the software development lifecycle
- Acceptance test plan: This document begins during the requirement phase and is completed at final delivery
- System test plan: This plan starts during the design plan and proceeds until the end of the project
- Integration and Unit test plan: Both these test plans start during the execution phase and last until the final delivery
Q151. Explain which test cases are written first black boxes or white boxes?
Ans: 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.
Q152. Explain what is the difference between latent and masked defects?
- Latent defect: A latent defect is an existing defect that has not caused a failure because the sets of conditions were never met
- Masked defect: It is an existing defect that has not caused a failure because another defect has prevented that part of the code from being executed
Q153. Mention what is bottom up testing?
Ans: 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.
Q154. Mention what are the different types of test coverage techniques?
Ans: Different three types of test coverage techniques include
- Statement Coverage: It verifies that each line of source code has been executed and tested
- Decision Coverage: It ensures that every decision in the source code is executed and tested
- Path Coverage: It ensures that every possible route through a given part of code is executed and tested
Q155. Mention what is the meaning of breadth testing?
Ans: Breadth testing is a test suite that exercises the full functionality of a product but does not test features in detail
Q156. Mention what is the difference between Pilot and Beta testing?
Ans: The difference between pilot and beta testing is that pilot testing is actually done using the product by the group of user 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.
Q157. Explain what is the meaning of Code Walk Through?
Ans: Code Walk Through is the informal analysis of the program source code to find defects and verify coding techniques
Q158. Mention what are the basic components of defect report format?
Ans: The basic components of defect report format includes
- Project Name
- Module Name
- Defect detected on
- Defect detected by
- Defect ID and Name
- Snapshot of the defect
- Priority and Severity status
- Defect resolved by
- Defect resolved on
Q159. Mention what is the purpose behind doing end-to-end testing?
Ans: End-to end testing is done after functional testing. The purpose behind doing end-to-end testing is that
- To validate the software requirements and integration with external interfaces
- Testing application in real world environment scenario
- Testing of interaction between application and database
Q160. Explain what it means by test harness?
Ans: A test harness is configuring a set of tools and test data to test an application in various conditions, it involves monitoring the output with expected output for correctness.
Q161. Explain in a testing project what testing activities would you automate?
Ans: In a testing project testing activities you would automate are
- Tests that need to be run for every build of the application
- Tests that use multiple data for the same set of actions
- Identical tests that needs to be executed using different browsers
- Mission critical pages
- Transaction with pages that do not change in short time