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. Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing






2. Testing software through executing it.






3. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers






4. The process of testing to determine the interoperability of a software product






5. A test suite that exercises the full functionality of a product but does not test features in detail






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






7. Determine whether a system meets some specified standard. external organization as complying with the standard






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






9. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






10. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.






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






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






13. Defined as any testing that occurs outside of the development environment. installed on. simply appear to be to run a setup program - can be used with confidence






14. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






15. This term refers to making software specifically designed for a specific locality






16. Kind of unit testing - internal working of software






17. A test that a user/sponsor and manufacturer/producer jointly perform on a finished - engineered product/system through black-box testing - as functional test & beta test & QA test & application test & confidence test & final test or end user test






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






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






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






21. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






22. Testing in which test cases are designed based on variable usage within the code.






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






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






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






26. A test that exercises a feature of a product in full detail.






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






28. The testing of individual software components.






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






30. Verifying a product is accessible to the people having disabilities (deaf or blind or mentally disabled etc.).






31. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.






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






33. Black-box tests conducted once the software has been integrated






34. Testing whether the system meets its specified objectives for maintainability.






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






36. A white box testing technique that exercises program loops






37. Application Under Test






38. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






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






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






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






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






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






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






45. Stakeholder stakeholder satisfaction with test results report






46. It is a whole - is the whole process form review to plans strategy and whole thing






47. Testing concerned with the accuracy of documentation.






48. executing the software






49. Testing one particular module - functionality heavily






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