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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






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






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






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






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






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






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






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






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






15. Actual inputs required to execute a test case






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






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






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






19. Combining components or sytems into larger structural units or subsystems.






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






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






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






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






24. Conditions required to begin testing activities.






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






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






27. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






45. Occurrences that happen before and after an unexpected event






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






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






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






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






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