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






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






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






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






5. Application Under Test






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






7. executing the software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






32. A white box testing technique that exercises program loops






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






34. Computer Aided Software Testing






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






36. Test case design






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






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






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






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






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






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






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






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






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






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






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






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. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






50. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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