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 decision outcomes that have been exercised by a test suite.






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






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






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






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






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






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






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






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






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






11. Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. extremely simple and free of preconceptions about system behavior.






12. Knows about the software and test - no proper plan






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






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






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






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






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






18. Application Under Test






19. Testing of programs or procedures used to convert data from existing systems for use in replacement systems.






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






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






22. Testing which covers all combinations of input values and preconditions for an element of the software under test






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






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






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






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






27. Testing one particular module - functionality heavily






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






29. Computer Aided Software Testing






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






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






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






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






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






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






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






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






38. Test activity aimed at proving the correct implementation of a required function at a level where the entire hardware/software chain involved in the execution of the function is available.






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






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






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






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






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






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






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






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






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






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






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






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







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