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. A task of maintaining and controlling changes to all entities of a system.






3. Conditions required to begin testing activities.






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






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






6. Deviation of a software system from its expected delivery services or results






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






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






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






10. Tools used by developers to identify defects in programs.






11. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






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






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






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






18. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






22. Calculates the number of executed branch outcomes in code.






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






24. Testing software in its operational environment






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






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






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






28. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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. Component - Integration - System - Acceptance






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






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






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






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






37. One defect prevents the detection of another.






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






39. A review not based on a formal documented procedure






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






41. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






49. Integration approach components or subsystems are combined all at once rather than in stages.






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