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. Calculates the number of executed branch outcomes in code.






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






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






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






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






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. Examine changes made to an operational system cause defects.






10. Response of the application to an input






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






12. A review not based on a formal documented procedure






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






14. Testing an integrated system to validate it meets requirements






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






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






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






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






19. Actual inputs required to execute a test case






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






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






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






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






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






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






26. Conditions required to begin testing activities.






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






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






29. A task of maintaining and controlling changes to all entities of a system.






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






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






32. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






35. Sequence in which instructions are executed through a component or system






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






37. Components are integrated in the order in which they are developed






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






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






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






41. Tests interfaces between components and between integrated components and systems.






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






43. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






45. Testing software in its operational environment






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






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






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






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






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