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. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






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






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






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






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






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






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






12. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






22. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






24. Occurrences that happen before and after an unexpected event






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






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






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






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. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






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






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






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






37. Testing an integrated system to validate it meets requirements






38. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






49. Component - Integration - System - Acceptance






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







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