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






2. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules






3. Stakeholder stakeholder satisfaction with test results report






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






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






6. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






7. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






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






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






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. A test case design technique for a component in which test cases are designed which include representatives of boundary values - the defined limits of an output domain.






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






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






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






16. Testing the changes to an operational system or the impact of a changed environment to an operational system






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






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






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






20. A testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations






21. Testing using input values that should be rejected by the component or system






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






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






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






25. executing the software






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






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






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






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






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






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






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






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






35. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






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






37. The process of testing to determine the efficiency of a software product






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






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






40. Informal method of usability inspection in the field of human-computer interaction. identifying the usability problems . involves evaluators examining the interface and judging its compliance






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






42. The testing of individual software components.






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






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






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






46. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-ofcode or number of classes or function points)






47. The typical grey box tester is permitted to set up or manipulate the testing environment - like seeding a database






48. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program path is available






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






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