In Agile, writing test cases can be little different as compared to other methodologies. We never get entire complete functionality to test because we build the functionalities in iterations and only part of the functionality is delivered in each Sprint (aka iteration).

So now whenever any Story is delivered in any Sprint. First thing a Tester must do is request the Programmer for a short Knowledge-Transition (K.T) session regarding this story. And we should cover the following points during the discussion:

1- What should be tested?

2- What should NOT be tested?

3- Any high risk areas?

4- Take a basic walk-through of the delivered feature.

(Note: Make sure all these discussions don’t take more than 5 min. So, prepare the questions in advance and then proceed with the discussion.)

  • Also, make sure that to test all the functionality in Cross-Browsers as well.

Now, writing Test-cases:

We should first find out all the possible scenarios first then we must start with the test case designing.

Here is an online post that has good Test scenario examples for commonly used functionality in Applications-

A Test case should contain following points:

1-Test Scenarios ID

2- Test Scenarios

3- Test Case ID

4- Test Case Objective

5- Steps Followed

6- Expected Result.

7- Actual Result.

8- Execution Result.

9- Comment

10- Retest status

(Note: Test case writing doesn’t have to be very detailed. Event short descriptions are also enough. )

Please check the Test-scenario and Testcases which I had written for some of our Projects.