1. What is Testing?
Testing is a set of activities conducted to find errors in software.

 
2. What is Test Plan?
A test plan is an important test asset used at different levels of testing. It details the scope and focus of testing at the specific level, completion criteria for testing, the test cases, and the elements of testing such as the test script and the test environment.
 
3. What is Test Case creation?
A test case is a set of inputs, execution conditions, and expected results that is designed for testing a particular aspect of a software product.
Test case creation is an activity performed while defining the testing strategy for a software project. This activity helps us ensure that the various data paths, conditions, branches, internal structures, and function calls in the software are executed appropriately.
 
4. What is Functionality Testing?
Functional Testing is the process of attempting to detect differences between a programs functional specification and it's actual behaviour. It verifies that the software provides expected service. Includes positive and negative scenarios i.e. valid inputs and invalid inputs.


5. What is Compatibility Testing?
Compatibility testing is typically defined in terms of hardware and software setup for testing.
And it ensures the functionality and reliability of the product on the supported browsers and platforms in place at the customer sites.
 
6. What is Regression Testing?
Regression testing is the activity of re-executing some or all test cases and checking the results for correctness. It helps check for any unintended side effects of changes made during testing.

7. What is Usability Testing?
Usability testing is testing for ‘user-friendliness’. Clearly this is subjective and depended on the target end-user or customer. User interviews, surveys, video recording of the user sessions and other techniques can be used. Programmers and developers are usually not appropriate as usability testers.
 
8. What is Defect Tracking and Documentation?
Defect Tracking begins by recording a variance from expectations; and will not be considered a true defect until the originator acknowledges the variance as an incorrect condition.
Defect Recording – Defect recording is used to describe and quantify deviations from requirements/expectations.
Defect Reporting – reports the status of defects; including severity and location.
Defect Tracking – monitoring defects from the time of recording until satisfactory resolution has been determined and implemented.
   
Copyright etesting 2009

services  l  company  l   experience  l   news  l   request  l  testing faq's  l   mail  l   sitemap