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. Conditions required to begin testing activities.






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






3. Testing software in its operational environment






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






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






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






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






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






9. Operational testing performed at an _external_ site without involvement of the developing organization.






10. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Linear Code Sequence and Jump.






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






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






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. All possible combinations of input values and preconditions are tested.






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






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. Increased load (transations) used to test behavior of system under high volume.






35. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






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






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






39. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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