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. A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes






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






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






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






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






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






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






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






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. Testing concerned with the accuracy of documentation.






12. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






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






24. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






29. Kind of unit testing - internal working of software






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






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. Testing conducted to evaluate whether systems or components pass data and control correctly to each other.






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






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






35. Testing a system or an Application on the fly - i.e just few tests here and there to ensure the system or an application does not crash out






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






37. Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.






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






39. Can't see - test the functional testing - no access to code and testing is done on UI






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






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






42. Testing carried out using no recognised test case design technique. It is also known as Exploratory Testing






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






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






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






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






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






48. Testing whether the system is compatible with other systems with which it should communicate.






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






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