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






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






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






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






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. Testing in which test cases are designed based on variable usage within the code.






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






8. Computer Aided Software Testing






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






10. A test case design technique for a component in which test cases are designed which include representatives of boundary values - the defined limits of an output domain.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






28. executing the software






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






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






31. The testing of individual software components.






32. Black box testing - concrete box or functional testing is used to check that the outputs of a program - given certain inputs - conform to the functional specification of the program. It performs testing based on previously understood requirements (or






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






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






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






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






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






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






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






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






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






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 white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes






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






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






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






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






49. Provide critical information during project






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