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. White-box design technique used to design test cases for a software component using LCSAJ.






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






3. Response of the application to an input






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






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






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






7. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






8. Waterfall iterative-incremental "V"






9. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






13. Actual inputs required to execute a test case






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






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






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






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






18. Events that occurred during the testing process our investigation.






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






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






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






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






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






24. Sequence in which data items are accessed or modified by code.






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






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






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






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






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






30. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






32. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






33. One defect prevents the detection of another.






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






35. Occurrences that happen before and after an unexpected event






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






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






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






39. Combining components or sytems into larger structural units or subsystems.






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






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






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






43. Software products or applications designed to automate manual testing tasks.






44. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






46. Conditions required to begin testing activities.






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






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






49. A review not based on a formal documented procedure






50. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes