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. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






5. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






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






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






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






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






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






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






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






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






16. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






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






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






24. A review not based on a formal documented procedure






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






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






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






28. The ratio between the number of defects found and the size of the component/system tested.






29. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






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






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






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






39. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






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






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






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






44. Response of the application to an input






45. Integrate different kinds of tools to make test management more efficient and simple.






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






47. Actual inputs required to execute a test case






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






49. Testing software components that are separately testable. Also module program and unit testing.






50. Component - Integration - System - Acceptance