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. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






3. Actual inputs required to execute a test case






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






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






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






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






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






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






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






11. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






23. Linear Code Sequence and Jump.






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






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






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






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






28. Response of the application to an input






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






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






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






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






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






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






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






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






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






38. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






42. Waterfall iterative-incremental "V"






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






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






45. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






48. Testing software in its operational environment






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






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