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. This term refers to making software specifically designed for a specific locality






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






3. Computer Aided Software Testing






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






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






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






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. Depends on the schedule and risk based - business impact follow the 20-80 rules






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






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






11. Stakeholder stakeholder satisfaction with test results report






12. Integration testing where system components are integrated into the system one at a time until the entire system is integrated.






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






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






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






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






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






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






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






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






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






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






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






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






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






26. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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






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






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






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






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






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






41. Testing concerned with the accuracy of documentation.






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






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






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






45. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






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






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






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






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






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






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