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. In software development testing is usually required before release to the general public. This is known as the alpha phase.alpha testing.






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






3. Once the alpha phase is complete development enters the beta phase. Versions of the software known as beta-versions are released to a limited audience outside of the company to ensure that the product has few faults or bugs. black box






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






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






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






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






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






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






10. The percentage of branches that have been exercised by a test suite. 100% - Implies both 100% decision coverage and 100% statement coverage






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






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






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






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






15. Kind of unit testing - internal working of software






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






17. Risk based questions - depends on the schedule and risk based - business impact follow the 20-80 rules






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






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






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






21. executing the software






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






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






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






25. The testing of individual software components.






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






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






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






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






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






31. Application Under Test






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






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






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






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






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






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






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






39. A service oriented architecture (SOA) is a design model which relies on a collection of loosely coupled self contained services that communicate with each other through the internet and can be called from multiple clients in a standard fashion






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






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






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






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






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






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






46. Stakeholder stakeholder satisfaction with test results report






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






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






49. Testing one particular module - functionality heavily






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