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






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






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






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






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






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






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






8. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






19. Response of the application to an input






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






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






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






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






24. Conditions required to begin testing activities.






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






26. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






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






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






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






34. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






36. A table showing combinations of inputs and their associated actions.






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






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






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






40. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






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






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






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






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






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






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






49. Linear Code Sequence and Jump.






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