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. This technique for testing computer software does not require significant advanced planning and is tolerant of limited documentation for the target-of-test.






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






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






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






5. Testing software through executing it.






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






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






8. Testing one particular module - functionality heavily






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






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






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






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






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






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






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






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






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






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






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






20. Testing concerned with the accuracy of documentation.






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






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






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






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






25. A white box test case design techniques that uses the algorithmic flow of the program to design tests






26. A white box testing technique that exercises program loops






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






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






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






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






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






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






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






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






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. The expected results or performance characteristics that define whether the test cases passed or failed






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






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






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






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






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






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






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






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






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






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






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






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. Testing which covers all combinations of input values and preconditions for an element of the software under test






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests