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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






7. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






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






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






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






13. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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






19. Severity - Priority






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






21. Testing an integrated system to validate it meets requirements






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






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






24. Linear Code Sequence and Jump.






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






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






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






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






29. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






43. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






44. Waterfall iterative-incremental "V"






45. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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






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






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