What are the Basic Testing Concepts

Some Basic Concepts on Testing

What is COTS?
 a.                    Commercial On-the-shelf software
b.                    Commercial off-the-shelf software
c.                    Common Offshore testing Software

Test coverage analysis is the process of 
  1. Creating additional test cases to increase coverage
  2. Finding areas of program exercised by the test cases
  3. Determining a quantitative measure of code coverage, which is a direct measure of quality.
  4. All of the above.
Critical in Web Testing
  1. Performance and Functionality
  2. Functionality and usability
  3. Usability and Performance
  4. None of the above
Class testing
  1. require a driver to test
  2. no need of instances of other classes
  3. no need to test the transitions
  4. all of the above.
Testing across different languages is called
  1. Linguistic Testing
  2. Localization Testing
  3. Both a and b
  4. None of the above.
Hierarchical System
  1. several levels of component that includes objects and classes
  2. several levels of component that includes objects, classes, systems
  3. several levels of component that includes, foundation components, systems
  4. none of the above.
Hybrid Testing
  1. combination of one or more testing techniques
  2. Combination of top-down and bottom-up testing
  3. Both a and b
  4. None of the above.
White Box Testing
  1. same as glass box  testing
  2. same as clear box testing
  3. both a and b
  4. none of the above.
Build Verification Test
  1. same as smoke test
  2. done after each build to make sure that the build doesn't contain major errors
  3. both a and b
  4. None of the above.
Content Testing
  1. Similar to proof reading
  2. Widely used in web testing
  3. Part of usability Testing
  4. All of the above
Decision Coverage.
  1. testing the boolean expressions which are not in control structures
  2. entire expression is considered as boolean expression irrespective of logical-and and logical-or operators
  3. coverage except switch-statement cases, exception handlers
  4. all of the above.
Branch Coverage
  1. another name for decision coverage
  2. another name for all-edges coverage
  3. another name for basic path coverage
  4. all the above
The following example is a 

if (condition1 && (condition2 || function1()))
  1. Decision coverage
  2. Condition coverage
  3. Statement coverage
  4. Path Coverage
Desk Checking 
  1. same as code walkthrough
  2. same as code inspection
  3. verification of code by the developers
  4. none of the above.
The benefits of glass box testing are 
  1. Focused Testing, Testing coverage, control flow
  2. Data integrity, Internal boundaries, algorithm specific testing
  3. Both a and b
  4. Either a or b
Structural Testing
  1. same as black box testing 
  2. same as white box testing
  3. same as functional testing
  4. none of the above.
Testing user documentation involves 
  1. Improved usability, reliability, maintainability
  2. Installability, scalability, liability
  3. Both a and b
  4. None of the above.
Identify which one is an internal failure  
  1. Delaying tester's access to areas of the code
  2. Replacement with updated product
  3. Training programmers to make or miss fewer bugs
  4. Testing by Tech. Support   
Smoke Testing 
  1. Same as build verification test
  2. To find that software is stable
  3. None of the above 
  4. To find whether the hardware burns out
Code Walkthrough
  1. a type of dynamic testing
  2. type of static testing
  3. neither dynamic nor static
  4. performed by the testing team
Static Analysis
  1. same as static testing
  2. done by the developers
  3. both a and b
  4. none of the above
User Acceptance Testing
  1. same as Alpha Testing
  2. same as Beta Testing
  3. combination of Alpha and Beta Testing
  4. none of the above 
Random Testing (K)     
a.  Program is tested randomly by sampling the input.
b.    A black-box testing technique
c.    Both a and b
d.    None of the above.

What is Error seeding 
  1. Evaluates the thoroughness with which a computer program is tested by purposely inserting errors into a supposedly correct program.
  2. Errors inserted by the developers intentionally to make the system malfunctioning.
  3. Neither a or b
  4. Both a and b
The post is continued at Basic Testing Concepts

For more articles on Manual Testing Log On to Manual Testing Articles

Post a Comment

Previous Post Next Post