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






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






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






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






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






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






7. executing the software






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






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






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






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






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






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






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






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






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






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






18. Form of independent - interoperable services that can be composed and recomposed to fulfill multiple business requirements. . Each service internally accesses resources including databases - business rules - client devices






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






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






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






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






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






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






25. Testing one particular module - functionality heavily






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






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






28. A white box testing technique that exercises program loops






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






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






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






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






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






34. Stakeholder stakeholder satisfaction with test results report






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






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






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






38. Computer Aided Software Testing






39. Application Under Test






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






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






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






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






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






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






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






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






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






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






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







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