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. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






5. Linear Code Sequence and Jump.






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






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






8. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






9. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






11. Testing software in its operational environment






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






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






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






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






16. Find defects in code while the software application being tested is running.






17. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






19. Testing an integrated system to validate it meets requirements






20. Occurrences that happen before and after an unexpected event






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






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






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






24. Tools used to identify and calculate coverage items in program code.






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






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






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






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






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






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






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






32. Examine changes made to an operational system cause defects.






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






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






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






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






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






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






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






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






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. A task of maintaining and controlling changes to all entities of a system.






44. Severity - Priority






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






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






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






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






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






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