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. GUI testing is the process of testing a graphical user interface to ensure it meets its written specifications






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






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






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






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






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






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






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






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






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






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






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






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






14. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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






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






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






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






27. Testing software through executing it.






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






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. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






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






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






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






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






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






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






38. Provide critical information during project






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






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






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






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






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






44. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion






45. Testing in which the action of a test case is parameterized by externally defined data values - maintained as a file or spreadsheet. A common technique in Automated Testing






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






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






48. Kind of unit testing - internal working of software






49. Application Under Test






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