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. The percentage of executable statements that have been exercised by a test suite.






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






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






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






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






6. executing the software






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






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






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






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






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. Test case design






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






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. Use analytical risk-based testing strategies - define realistic objectives for testing - with metrics - Instititutes continuous test process improvement based on lessons learned






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






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






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






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






21. Testing one particular module - functionality heavily






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






23. A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+.






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






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






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






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






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






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






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






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






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






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






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






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






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






38. Application Under Test






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






40. Root cause analyst - base of the problem - customer satisfaction report






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






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






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






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






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






46. Testing software through executing it.






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






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






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






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