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






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






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






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






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






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






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






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






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






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






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






12. Occurrences that happen before and after an unexpected event






13. Conditions required to begin testing activities.






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






15. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






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






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






22. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






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






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






25. One defect prevents the detection of another.






26. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






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






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






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






36. Severity - Priority






37. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






42. Waterfall iterative-incremental "V"






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






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






45. Testing software in its operational environment






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






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






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






49. Response of the application to an input






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