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 scripting technique that uses data files to contain not only test data and expected results but also keywords related to the application being tested.






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






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






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






5. An organizational structure consists of activities such as task allocation & coordination and supervision which are directed towards the achievement of organizational aims.[citation needed]






6. Computer Aided Software Testing






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






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






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






10. Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration






11. Application Under Test






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






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






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






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






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






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






18. executing the software






19. A white box testing technique that exercises program loops






20. Testing one particular module - functionality heavily






21. Provide critical information during project






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






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






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






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






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






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






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






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






30. Test case design






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






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






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






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






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






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






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






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






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






40. The percentage of decision outcomes that have been exercised by a test suite.






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. This term refers to making software specifically designed for a specific locality






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






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






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






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






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






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






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






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