Test cases for effective testing - part 1

Test cases For effective testing

Prepared by:Mona M. Abd El-Rahman.QC Engineer at Ibtikar Technologies Co.

Part 1

What is a Test Case

A test case has components that describes an input, action or event and an expected response, to determine if a feature of an application is working correctly.

Why Test Cases are important

Which features have been tested/ will be tested eventually?

How many user scenarios/ use cases have been executed?

How many features are stable?

Which features need more work?

Are sufficient input combinations exercised?

Does the app give out correct error messages if the user does not use it the way it was intended to be used?

Does the app respond to the various browser specific functions as it should?

Does the UI conform to the specifications?

Are the features traceable to the requirement spec? Have all of them been covered?

Are the user scenarios traceable to the use case document? Have all of them been covered?

Can these tests be used as an input to automation?

Are the tests good enough? Are they finding defects?

Is software ready to ship? Is testing enough?

What is the quality of the application?

Approaches of writing test cases:

Function: Test each function/ feature in isolation.

Domain : Test by partitioning different sets of values.

Specification based: Test against published specifications.

Risk based: Imagine a way in which a program could fail and then design tests to check whether the program will actually fail.

Scenario/ use case based: Based on actors/ users and a set of actions they are likely to perform in real life.

Exploratory: the tester actively controls the design of tests as those tests are performed and uses information gained while testing to design new and better test.

User: Tests done by users.

Approaches (Cont’d)

How to write a Test Case

Understand the requirements well.

( while writing test cases do not assume any requirements by your own. Raise the question which is not clear in requirement or requirements are misleading or incomplete. )

Prior to design the test cases figure out all features of application.

Ensure that test case should cover all functionality mention in requirement document.

- Checklists. - Traceability Metrix.

Generic test cases should be collected & combine together in test suite.

Testing Priority should be assign to each test case. (Select the Test case priority depending upon how important the

test case is for that Feature, component or the product).

Test cases should be simple and easy to understand.

Input data for test cases is very important part in testing, your test cases should validate range of input data.

You should concentrate on real life scenarios first which end user going to use day to day life activity and accordingly test cases should be prepare.

Every test case may or may not have defect linked but each defect should have test case linked.

Test case id. Test case title. Summary. Pre-conditions and test data. Test case steps. Test case expected results.

Test case format:

Test case title should start with Upper Case. Each step should start with Upper Case. Use parameter’s names as it is instead of using

generic names. Start with module name then write the title.

Ex. Login – Error message must be displayed when user inserts a wrong password.

Use must/ would instead of should/ may.

Test case naming convention:

Workshop

Image Upload Functionality

Activity 1:

Sending Emails

Activity 2:

Search/ Filter

Activity 3:

Logout

Activity 4:

Export PDF

Activity 5:

Different time zones

Activity 6:

For any questions, feel free to contact memona.m.abdelrahman@gmail.com