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 based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






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






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






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






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






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






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






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






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






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






14. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






16. One defect prevents the detection of another.






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






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






19. Waterfall iterative-incremental "V"






20. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






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






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






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






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






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






28. Deviation of a software system from its expected delivery services or results






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






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






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






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






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






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






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






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






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






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






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






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






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






42. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






47. Linear Code Sequence and Jump.






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






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






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