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. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






20. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






26. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






27. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






29. Response of the application to an input






30. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






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






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






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






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