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






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






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






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






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






6. Actual inputs required to execute a test case






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






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






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






10. Sequence in which instructions are executed through a component or system






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






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






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






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






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






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






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






18. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






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






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






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






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






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






26. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






27. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






34. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






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






47. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






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