welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...

image
Blog

Guidelines to write an effective test case

By Himanshu on 2/3/2014

Ability to write effective test case it can be acquire by testing experience and carefully studying the requirement and the software that is going through test. In this blog I will discuss how to write an effective test case. While creating a test case it should be well categorized like functional, business, navigational, validation error, etc.  To get a better understanding to the case as looking to its category user will know it is related to which part of the application/software. 

Let me first describe what is a test case? A test case is a set of actions with expected result and actual result, a bug is created when the actual result differs from the expected result when going through a test case.

  •  It is very essential to have the understanding of the requirement while writing the test case do not just assume some requirement and create  a test case  these  types of assumption should be avoided.
  •  Assumptions should only be based on the requirements. Any requirements which are not clear ask them to BA business requirement. Testers should not ask  these questions to developers.
  •  The test case should cover asked functionality mention in SRS document.
  •  Avoid creation duplicate test cases.
  •  Cases which are generic should be combined together to a test suite, It helps to reduce the effort of writing common test cases each time also be re used over  and over again.
  •  Testing Priority should always be put in test case. When these cases will be test then high priority test cases are tested first then medium and Low priority ones  later.
  •  Writing test cases tester should keep in mind that test cases should be simple and stress-free to understand. Test cases should not be written as or  explanations like essays. It should be point to point try to keep it short and understandable.
  •  The test input data is also very important the input data should validate the range of input value. Test case should also check the systems behaviour in normal  and abnormal conditions.
  •  When creating test cases a tester should focus on real life scenarios first which includes day to day activity which will be performed by software.
  •  One last thing to keep in mind “Every test case may or may not have defect/bug created to it, but each defect/bug should have test case related to it.”

 Every test case should have these following details:

  • Test case id – (Unique Identifier for the case in PSD system)
  • Test case Title – (It is a short description of test case)
  • Test case Summary – (Full explanation of test case and additional facts/figures required for the test case to be executed)
  • Test Steps – (Actual scenario step to be executed)
  • Test Priority – (High priority, medium and Low priority)
  • Excepted Result – (Normal result expected these result)
  • Actual result – (Current findings from the test)
  • Test Case Status(Pass/Fail)
  • Comments/Remark’s – (Additional tester Comments)

 

Testing Tools
good and effective test
Guidelines to write an effective test case
how to write test case
Author
Blog Calendar
Blog Calendar List
2020 Apr  10  3
2020 Feb  18  4
2020 Jan  22  7
2019 Dec  15  4
2019 Nov  11  1
2019 Jan  31  3
2018 Dec  31  4
2018 Nov  66  3
2018 Oct  12  3
2018 Sep  192  11
2018 Aug  6  2
2018 Jun  11  1
2018 Jan  53  2
2017 Sep  544  5
2017 Aug  17  1
2017 Jul  17  2
2017 Jun  51  2
2017 May  21  1
2017 Apr  32  2
2017 Mar  118  4
2017 Feb  411  4
2016 Dec  177  3
2016 Nov  366  8
2016 Oct  240  10
2016 Sep  362  6
2016 Aug  39  1
2016 Jun  1754  6
2016 May  104  3
2016 Jan  70  2
2015 Dec  392  6
2015 Nov  4  1
2015 Oct  13  1
2015 Sep  1319  6
2015 Aug  13  1
2015 Jul  124  2
2015 Jun  10  1
2015 May  20  1
2015 Apr  28  3
2015 Mar  78  3
2015 Jan  5195  4
2014 Dec  17  1
2014 Nov  2212  4
2014 Oct  63  1
2014 Sep  104  2
2014 Aug  3986  1
2014 Jul  46  2
2014 Apr  2458  12
2014 Mar  284  19
2014 Feb  237  8
2014 Jan  1510  16
2013 Dec  21  2
2013 Nov  635  2
2013 Oct  250  3
2013 Sep  11  1
2013 Aug  37  3
2013 Jul  207  1
2013 Apr  49  6
2013 Mar  1827  10
2013 Feb  302  4
2013 Jan  262  2
2012 Nov  32  2
2012 Oct  444  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote