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






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






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






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






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






6. Kind of unit testing - internal working of software






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






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






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






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






11. Application Under Test






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






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






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






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






16. Test case design






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






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. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






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






23. Computer Aided Software Testing






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






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






26. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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