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. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






2. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






14. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






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






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






23. Black-box test design technique - test cases are designed from a decision table.






24. Incident Report - Identifier - Summary - Incident - Description - Impact






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






26. A review not based on a formal documented procedure






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






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






29. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






30. An event or item that can be tested using one or more test cases






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






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






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






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






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






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






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






38. Actual inputs required to execute a test case






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






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






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






42. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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