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. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






4. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






14. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






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






18. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






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






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






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






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






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






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






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






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






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






30. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






34. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






39. Linear Code Sequence and Jump.






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






41. One defect prevents the detection of another.






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






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






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






45. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






46. Human action that generates an incorrect result.






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






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






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






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