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. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






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






6. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. Occurrences that happen before and after an unexpected event






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






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






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






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






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






27. Waterfall iterative-incremental "V"






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






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






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






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






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






33. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






43. Linear Code Sequence and Jump.






44. A table showing combinations of inputs and their associated actions.






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






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. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






50. Severity - Priority