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. Component testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs






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






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 practice for projects using agile methodologies - treating development as the customer of testing and emphasizing a test-first design paradigm






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






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






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






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






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






10. Testing software through executing it.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






25. Multi-user testing geared towards determining the effects of accessing the same application code - module or database records. Identifies and measures the level of locking - deadlocking and use of single-threaded code and locking semaphores






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






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






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






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






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






32. Stakeholder stakeholder satisfaction with test results report






33. The testing of individual software components.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Approach to doing something that generally give good results when applied appropriately and thoughfully






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






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests