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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






3. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






6. Waterfall iterative-incremental "V"






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






8. Human action that generates an incorrect result.






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






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






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






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






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






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






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






16. Conditions required to begin testing activities.






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






18. Special-purpose software used to simulate a component that calls the component under test






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






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






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






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






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






24. All possible combinations of input values and preconditions are tested.






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






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






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






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






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






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






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






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






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






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






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






36. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






43. Sequence in which data items are accessed or modified by code.






44. Response of the application to an input






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






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






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






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






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






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