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






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






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






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






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






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






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






8. All about code and profiler & comments in the code naming convention etc... coding standards.It is like transparent






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






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






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






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






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






14. The expected results or performance characteristics that define whether the test cases passed or failed






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






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






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






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






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






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






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






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






23. Test case design






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






25. The testing of individual software components.






26. Testing which covers all combinations of input values and preconditions for an element of the software under test






27. Testing one particular module - functionality heavily






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






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






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






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






32. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






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






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






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






46. Back end Testing means DataBase Testing. Normally a software product/application uses GUI front end for easyuser interaction.






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






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






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






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