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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






3. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






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






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






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






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






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






9. Testing an integrated system to validate it meets requirements






10. Measures amount of testing performed by a collection of test cases






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






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






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






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






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






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






17. Input or combination of inputs required to test software.






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






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






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






21. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






22. Linear Code Sequence and Jump.






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






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






25. Waterfall iterative-incremental "V"






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






27. Actual inputs required to execute a test case






28. A set of conditions that a system needs to meet in order to be accepted by end users






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






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






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






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






33. Testing software in its operational environment






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






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






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






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






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






39. The smallest software item that can be tested in isolation.






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






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






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






43. Response of the application to an input






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






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






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






47. Testing performed to determine whether the system meets acceptance criteria






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






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






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