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 case design techniques that uses the algorithmic flow of the program to design tests






2. Computer Aided Software Testing






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






4. Testing concerned with the accuracy of documentation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. Kind of unit testing - internal working of software






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






45. Stakeholder stakeholder satisfaction with test results report






46. A white box testing technique that exercises program loops






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






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






49. Approach to doing something that generally give good results when applied appropriately and thoughfully






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