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. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






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






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






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






12. Application Under Test






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






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






15. executing the software






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






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






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






19. Computer Aided Software Testing






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






21. Kind of unit testing - internal working of software






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






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






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






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






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






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






28. A white box testing technique that exercises program loops






29. Examines an application's requirements for pre-existing software - initial states and configuration in order to maintain proper functionality






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






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






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






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






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






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






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






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






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






39. Provide critical information during project






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






41. Coverage testing is concerned with the degree to which test cases exercise or cover the logic (source code) of the software module or unit. It is also a measure of coverage of code lines & code branches and code branch combinations






42. Testing software through executing it.






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






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






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






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






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






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






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






50. Testing one particular module - functionality heavily






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