Test your basic knowledge |

Software Testing And Qa

Subject : it-skills
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. executing the software






2. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box






3. Measure of amount of testing performed . determined by mapping test cases to requirements - Tracebility matrix is test coverage. Number of test caes executed divided by total number of test cases






4. A white box test design technique in which test cases are designed to execute branches.






5. Model-based testing refers to software testing where test cases are derived in whole or in part from a model that describes some (usually functional) aspects of the system under test.






6. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






7. Root cause analyst - base of the problem - customer satisfaction report






8. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared and analyzed in cases of discrepancies






9. Testing software through executing it.






10. Provide critical information during project






11. An approach to integration testing where the lowest level components are tested first - then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.






12. Kind of unit testing - internal working of software






13. The testing of individual software components.






14. A white box test design technique in which test cases are designed to execute decision outcomes






15. A black box test design techniques in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table






16. The percentage of decision outcomes that have been exercised by a test suite.






17. Testing practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






18. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






19. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.






20. A white box test case design techniques that uses the algorithmic flow of the program to design tests






21. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






22. Depends on the schedule and risk based - business impact follow the 20-80 rules






23. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






24. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.






25. An anomaly or flaw in a delivered work product. found during early lifecycle phases A defect can be any kind of issue you want tracked and resolved.






26. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






27. Checks for memory leaks or other problems that may occur with prolonged execution






28. Approach to doing something that generally give good results when applied appropriately and thoughfully






29. A system under load. modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently.






30. The totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs." defined by ISO 8402 1986






31. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes






32. Gamma testing is a little-known informal phrase that refers derisively to the release of "buggy" (defect-ridden) products.






33. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






34. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






35. Knows about the software and test - no proper plan






36. Involves testing the systems responsible for the initiation and maintenance of user sessions. This will require testing the Input validation of login fields & Cookie security and Lockout testing . permitting unauthorised access.






37. They arise from mistakes and errors made by people in either a program's source code or its design that prevents it from working correctly or produces an incorrect result






38. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.






39. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.






40. The percentage of executable statements that have been exercised by a test suite.






41. The expected results or performance characteristics that define whether the test cases passed or failed






42. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






43. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores






44. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






45. Testing which covers all combinations of input values and preconditions for an element of the software under test






46. Testing concerned with the accuracy of documentation.






47. A scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






48. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration






49. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






50. An accidental condition that causes the failure of a component in the implementation model to perform its required behavior. A fault is the root cause of one or more defects identified by observing one or more failures.