Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Sequence in which instructions are executed through a component or system






2. The process of finding analyzing and removing causes of failure in a software product.






3. Integration approach components or subsystems are combined all at once rather than in stages.






4. All possible combinations of input values and preconditions are tested.






5. A unique identifier for each incident report generated during test execution.






6. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






7. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






8. Develop & proiroitize test cases Create groups of test cases Set up test environment






9. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






10. White-box design technique used to design test cases for a software component using LCSAJ.






11. A functional testing approach in which test cases are designed based on business processes.






12. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






13. Input or combination of inputs required to test software.






14. Informal testing technique in which test planning and execution run in parallel






15. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






16. Allows storage of test input and expected results in one or more central data sources or databases.






17. Ability of software to provide appropriate performance relative to amount of resources used.






18. A component of the incident report that determines the actual effect of the incident on the software and its users.






19. A task of maintaining and controlling changes to all entities of a system.






20. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






21. Conditions required to begin testing activities.






22. Specific groups that represent a set of valid or invalid partitions for input conditions.






23. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






24. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






25. Based on analysis of functional specifications of a system.






26. Incident Report - Identifier - Summary - Incident - Description - Impact






27. Process used to create a SW product from initial conception to public release






28. Used to test the functionality of software as mentioned in software requirement specifications.






29. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






30. Black-box testing technique used to create groups of input conditions that create the same kind of output.






31. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






32. Response of the application to an input






33. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






34. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






35. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






36. An event or item that can be tested using one or more test cases






37. Requirements that determine the functionality of a software system.






38. A set of conditions that a system needs to meet in order to be accepted by end users






39. Components are integrated in the order in which they are developed






40. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






41. Special additions or changes to the environment required to run a test case.






42. Deviation of a software system from its expected delivery services or results






43. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






44. Used to replace a component that calls another component.






45. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






46. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






47. One defect prevents the detection of another.






48. Human action that generates an incorrect result.






49. Components are combined and tested in the order in which basic functionalities start working






50. Special-purpose software used to simulate a component that calls the component under test