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. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






12. Testing software through executing it.






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






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






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






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






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






18. Testing one particular module - functionality heavily






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






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






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






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. Can't see - test the functional testing - no access to code and testing is done on UI






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






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






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






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






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






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






30. Designing tests based on objectives derived from the architectural or detail design of the software (e.g. - tests that execute specific invocation paths or probe the worst case behaviour of algorithms).






31. Testing concerned with the accuracy of documentation.






32. The testing of individual software components.






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






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






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






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






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






38. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






43. Application Under Test






44. Formal or informal testing conducted during the implementation of a component or system usually in the development environment by developers






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






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






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






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






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests