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. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






3. Tools used by developers to identify defects in programs.






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






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






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






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






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






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






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






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






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






13. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






15. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






25. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






26. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






27. A review not based on a formal documented procedure






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






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






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






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






32. Record details of test cases executed Record order of execution record results






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






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






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






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






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






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






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






40. Occurrences that happen before and after an unexpected event






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






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






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






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






45. Conditions required to begin testing activities.






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






47. Testing software in its operational environment






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






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






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