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. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






3. Testing concerned with the accuracy of documentation.






4. Test case design






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






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






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






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






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






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






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






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






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






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






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






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






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






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






19. Computer Aided Software Testing






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






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






22. The testing of individual software components.






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






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






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






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






27. Kind of unit testing - internal working of software






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






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






31. executing the software






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






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






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






35. Stakeholder stakeholder satisfaction with test results report






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






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






38. Testing software through executing it.






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






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






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






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






43. Testing one particular module - functionality heavily






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






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






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






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






48. Application Under Test






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






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