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 white box test design technique in which test cases are designed to execute branches.






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






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






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






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






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






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






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






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






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






11. Provide critical information during project






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






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






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






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






16. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






35. The testing of individual software components.






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






37. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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






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