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






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






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






4. Stakeholder stakeholder satisfaction with test results report






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






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






8. executing the software






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






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






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






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






13. A white box testing technique that exercises program loops






14. Testing one particular module - functionality heavily






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






17. A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification






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






19. Similar to black box testing - structure of test cases in order to find defects and its strutured






20. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






41. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






49. Testing concerned with the accuracy of documentation.






50. Testing software through executing it.