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






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






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






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






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






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






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






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






9. Severity - Priority






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






11. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






16. Waterfall iterative-incremental "V"






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






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






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






20. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






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






31. One defect prevents the detection of another.






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






33. Human action that generates an incorrect result.






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






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






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






37. Special additions or changes to the environment required to run a test case.






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






39. Requirements that determine the functionality of a software system.






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






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






42. Components are combined and tested in the order in which basic functionalities start working






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






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






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests