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 ratio between the number of defects found and the size of the component/system tested.






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






3. Testing software in its operational environment






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






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






6. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






15. Severity - Priority






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






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






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






19. One defect prevents the detection of another.






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






21. Component - Integration - System - Acceptance






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






23. Linear Code Sequence and Jump.






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






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






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






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






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






29. A review not based on a formal documented procedure






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






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






32. Testing an integrated system to validate it meets requirements






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






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






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






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






37. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






40. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






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






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






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






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






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