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. Process used to create a SW product from initial conception to public release






2. Component - Integration - System - Acceptance






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






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






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






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






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






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






9. Events that occurred during the testing process our investigation.






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






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






12. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






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






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






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






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






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






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






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






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






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






23. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






39. Severity - Priority






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






41. A review not based on a formal documented procedure






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






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






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






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






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






47. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






48. Response of the application to an input






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






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