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 document that records the description of each event that occurs during the testing process and that requires further investigation






2. Severity - Priority






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






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






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






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






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






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






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






10. Requirements that determine the functionality of a software system.






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






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






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






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






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






16. Occurrences that happen before and after an unexpected event






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






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






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






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






21. Black-box test design technique - test cases are designed from a decision table.






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






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






24. Testing software in its operational environment






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






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






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






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






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






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






31. Response of the application to an input






32. Special-purpose software used to simulate a component that calls the component under test






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






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






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






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






37. Component - Integration - System - Acceptance






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






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






40. Testing an integrated system to validate it meets requirements






41. A review not based on a formal documented procedure






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






43. Measures amount of testing performed by a collection of test cases






44. Human action that generates an incorrect result.






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






46. Special additions or changes to the environment required to run a test case.






47. Linear Code Sequence and Jump.






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






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






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