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. One defect prevents the detection of another.






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






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






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






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






6. Occurrences that happen before and after an unexpected event






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






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






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






10. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






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






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






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






18. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






19. Tools used by developers to identify defects in programs.






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






21. Severity - Priority






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






23. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






26. Testing software in its operational environment






27. Testing an integrated system to validate it meets requirements






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






29. A technique used to improve testing coverage by deliberately introducing faults in code.






30. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






31. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






34. An analysis that determines the portion of code on software executed by a set of test cases






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






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






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






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






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






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






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






42. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






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






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






45. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






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






48. Actual inputs required to execute a test case






49. The smallest software item that can be tested in isolation.






50. Tools used to store and manage incidents return phone defects failures or anomalies.