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. Find defects in code while the software application being tested is running.






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






3. One defect prevents the detection of another.






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






5. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






10. Conditions required to begin testing activities.






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






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






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






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






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






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






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






18. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






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






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






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






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






28. Component - Integration - System - Acceptance






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






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






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






32. Response of the application to an input






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






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






35. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






39. A table showing combinations of inputs and their associated actions.






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






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






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






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






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






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






46. Testing software in its operational environment






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






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






49. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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