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. Separation of testing responsibilities which encourages the accomplishment of objective testing






2. Conditions required to begin testing activities.






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






4. Linear Code Sequence and Jump.






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






6. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






28. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






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






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






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






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






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






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






38. Human action that generates an incorrect result.






39. One defect prevents the detection of another.






40. Occurrences that happen before and after an unexpected event






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






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






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






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






45. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






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