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. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






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






4. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






27. An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.






28. Provide critical information during project






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Application Under Test






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






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






47. Testing which covers all combinations of input values and preconditions for an element of the software under test






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






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






50. Kind of unit testing - internal working of software







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