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. A test that exercises a feature of a product in full detail.






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






3. The testing of individual software components.






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






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






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






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






8. Application Under Test






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






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






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






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






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






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






15. Testing one particular module - functionality heavily






16. A white box testing technique that exercises program loops






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






18. Provide critical information during project






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






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






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






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






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






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






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






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






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






28. A test case design technique for a component in which test cases are designed to execute branch outcomes. A test method satisfying coverage criteria that require that for each decision point - each possible branch be executed at least once.






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






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






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






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






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






34. Testing concerned with the accuracy of documentation.






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






36. Test case design






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






38. executing the software






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






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






41. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






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






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