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






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






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






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






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






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






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






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






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






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






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. The process of testing to determine the interoperability of a software product






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






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






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






16. Stakeholder stakeholder satisfaction with test results report






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






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






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






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






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






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






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






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






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






26. Testing software through executing it.






27. Computer Aided Software Testing






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






50. Test case design