Sample TestCases for Software Testing

TestCases for Yahoo messenger:

-------------------------------------------

1. verify to login

2. verify to add contact is working

3. send a message to contact available online and offline

4. send a file 

5. add an existing contact6. verify the settings

7. verify the contacts available online and and available(offline)

8. verify to delete contact

9. verify to add group

TestCase for mobile phone:

--------------------------------------

1.Check whether the dimensions of mobile are according to the requirements.

2.Check whether the colour is accroding to requirments.

3.Check whether the functionalities are with respect to the requirements.

4.Check whether the backup for battery is as given in the manual.

5.Check whether the functionalities are with respect to the manual.(extras,games,email services,bluetooth,camera etc.)

6.Checking for various items as charger,headphones,cable etc.

7.checking for display colour(B/w or colour) of the mobile as mentioned in requirements.

8.check whether the functionality of keys are proper.

9.check whether the model is according to the requirements.

10.check for memory used for storage.

11.checking out for memory where data is stored above the peak value.

12.checking for proper signal and network in maximum areas.

13.checking for performance of the mobile.

14.checking for the usability.

TestCases for Telephone:

------------------------------------

1.Lift the handset, u should get a tone.

2.Dial the number again u should here the dial tones

3.If the number is busy, in active, or any such issues you should get an alert about the same

4.If no such alerts , you should here riging tone in the hand set.

5.If it rings for a long time n destination doesnt picks up the call, an alert should be given.

6.If not the above case, at destination user must lift the phone.

7.When he lifts the phone ringing tone must be ended.

8.Now talking session must take place.

9.Both src and destination user can talk n hear properly.

10.If any one of them closes the session, again a tone must be heard at the other end.

11.Close of session in between

IBM's ETVX Concept

ETVX Concept

         IBM has introduced this ETVX model in 80's to document their processes.

'E' stands for the entry criteria which must be satisfied before a set of tasks can be performed.

         Ex: Like Approved SRS/FRS documents are required for the design of application / for Testing

  'T' is the set of tasks / procedures to be performed

          Ex: tasks include design test cases, reviews...etc

 'V' stands for the verification & validation process to ensure that the right tasks are performed
          Ex: validate the application as per the requirements and review the testing

 'X' stands for the exit criteria or the outputs of the tasks.

          Ex: The documents prepared like Test Log / defect reports / Test summary reports...etc

 If an activity fails in the validation check, either corrective action is taken or a rework is ordered. It can be used in any development process. Each phase in the process can be considered as an activity and structured using the ETVX model. If required, the tasks can be further subdivided and each subtask can be further structured using the ETVX model

Ganapathi books now

Calculate the Quality of the application:

Testing Metrics

Metrics used in Software Testing

Metric is a measurement of unit for calculating the Quality of project, process..etc
Metric is calculated using the formula

Below are few of the metrics

Test Coverage = Number of units (KLOC/FP) tested / total size of the system. (LOC represents Lines of Code)

Number of tests per unit size = Number of test cases per KLOC/FP (LOC represents Lines of Code).

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria

Defects per size = Defects detected / system size

Test cost (in %) = Cost of testing / total cost *100

Cost to locate defect = Cost of testing / the number of defects located

Achieving Budget = Actual cost of testing / Budgeted cost of testing

Defects detected in testing = Defects detected in testing / total system defects

Defects detected in production = Defects detected in production/system size

Quality of Testing = No of defects found during Testing/(No of defects found during testing + No of acceptance defects found after delivery) *100

Effectiveness of testing to business = Loss due to problems / total resources processed by the system.

System complaints = Number of third party complaints / number of transactions processed

Scale of Ten = Assessment of testing by giving rating in scale of 1 to 10

Source Code Analysis = Number of source code statements changed / total number of tests.

Effort Productivity = Test Planning Productivity = No of Test cases designed / Actual Effort for Design and Documentation

Test Execution Productivity = No of Test cycles executed / Actual Effort for testing

Testing :
                To verify the application as per customer requirements.
Software Testing:
                To verify the application working as per Functional requirement specification document (FRS).