Monday 10 December 2012

Software Testing life cycle





                        TESTING LIFE CYCLE

  1. REQUIREMENT ANALYSIS- In this phase the requirements of the client are determined.
  1. DESIGN ANALYSIS-In this phase the testers works with the developers in order to determine what aspects of the design are testable.
  1. TEST PLANNING- In this phase various test plans are made.
  1. TEST DEVELOPMENT-In phase various test cases are define.
  1. TEST EXECUTION:The testers execute the tests on the software and then report errors to the development team.
  1. TEST REPORTING-Once the testing have been performed then metrics are generated and various test reports are written on their testing efforts and to check that whether the software is ready to release or not.
  1. RECHECKING THE DEFECTS-The defects are checked once again to verify.



TEST Metrics



Test Metrics can be used to measure test coverage prior to software delivery. It provides a measure of the percentage of the software tested at any point during testing.
It is calculated as follows:
Functional 

Test Coverage = number of test requirements that are covered/total number of test requirements.

 

Types of Test metrics


Software Release Metrics
The software is ready for release when:
1. It has been tested with a test suite that provides 100% functional coverage, 80% branch coverage, and 100% procedure coverage.
2. There are no level 1 or 2 severity defects.
3. The defect finding rate is less than 40 new defects per 1000 hours of testing
4. Stress testing, configuration testing, installation testing, Naïve user testing, usability testing, and sanity testing have been completed
 

Wednesday 5 December 2012

SELF JOIN EXPANATION


What is a self join? Explain it with an example

Let’s illustrate the need for a self join with an example. Suppose we have the following table – that is called employee. The employee table has 2 columns – one for the employee name (called employee_name), and one for the employee location (called employee_location):
employee
employee_name
employee_location
Joe
New York
Sunil
India
Alex
Russia
Albert
Canada
Jack
New York
Now, suppose we want to find out which employees are from the same location as the employee named Joe. In this example, that location would be New York. Self join

SELECT e1.employee_name
FROM employee e1, employee e2
WHERE e1.employee_location = e2.employee_location
AND e2.employee_name="Joe";

Working of Query.


Well, we want to find all the employees who have the same location as Joe – so if we are doing a join we would want to make sure that the location is the same and that the employee name is Joe. So, our join predicate would be where e1.employee_location = e2.employee_location AND employee_name = "Joe". Note that e1 and e2 will represnt the 2 employee tables that we are doing a self join on.