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. Separation of testing responsibilities which encourages the accomplishment of objective testing






2. Increased load (transations) used to test behavior of system under high volume.






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






4. Occurrences that happen before and after an unexpected event






5. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






7. The capability of a software product to provide agreed and correct output with the required degree of precision






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






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






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






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






12. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






13. Waterfall iterative-incremental "V"






14. Integrate different kinds of tools to make test management more efficient and simple.






15. Sequence in which instructions are executed through a component or system






16. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






17. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






18. 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






19. Black-box test design technique - test cases are designed from a decision table.






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






21. Testing software components that are separately testable. Also module program and unit testing.






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






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






24. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






25. Tests interfaces between components and between integrated components and systems.






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






27. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






28. Testing performed to determine whether the system meets acceptance criteria






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






30. Linear Code Sequence and Jump.






31. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






32. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






33. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






35. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






36. Insertion of additional code in the existing program in order to count coverage items.






37. Actual inputs required to execute a test case






38. Measures amount of testing performed by a collection of test cases






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






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






41. A document that provides the structure for writing test cases.






42. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






43. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






45. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






46. Calculates the number of executed branch outcomes in code.






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






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






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






50. Record details of test cases executed Record order of execution record results