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






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






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






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






6. Flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.






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






8. Provide critical information during project






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






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






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






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






13. Testing whether the system is compatible with other systems with which it should communicate.






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






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






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






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






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






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






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






21. executing the software






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






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






24. Kind of unit testing - internal working of software






25. The percentage of executable statements that have been exercised by a test suite.






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






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






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






29. Computer Aided Software Testing






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






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






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






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






34. A white box testing technique that exercises program loops






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






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






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






38. Application Under Test






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






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






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






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






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






44. Test case design






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






46. The testing of individual software components.






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






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






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






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