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. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






3. executing the software






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






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






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






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






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






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






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






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






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






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






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






15. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






27. Checks for memory leaks or other problems that may occur with prolonged execution






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






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






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






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






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






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






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






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






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






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






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






39. Application Under Test






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






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






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






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






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






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






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






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






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






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






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







Sorry!:) No result found.

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