Project Management

What is good to have in a Test Case:

From the Blog for Project Management Practices by Pravin Blog
by
Project Management Practices, Stories, Learning about Project and Program management. How to deliver value and getting best from your team.

About this Blog

RSS

Recent Posts

Rethinking Project Leadership in a Dynamic World

Software Product Upgrades

Welcome 2022!

Challenges in recent times - Work from home

Software: Reopen Defects

Categories

PMO, Quality, Requirements Management, Software Products, Test Case, Use Cases

Date

linkedin twitter facebook Request to reuse this  


Test Case is a scenario created to validate or test any program using sample data. The outcome of the test case determines whether the test is successful or failed. Successful execution of test case implies that business requirements met and program produces the desired results.

It is imperative to have test cases efficient, covering all the aspects of programs in order to validate. A test case may contain multiple steps.

Following are the characteristics of a test case:

  1. Completeness – A test case should be thorough, having necessary steps covering the requirements and business cases, clear mapping with requirements i.e. use cases.
  2. Clarity – Easy to understand and anyone can execute it.
  3. Sufficient Data – It must contain sufficient data perform test. Without sufficient and meaningful data a test case becomes inefficient and there are chances to overlook important data validations.
  4. Reference to dependent cases – Sometimes it is required to execute the other test cases to complete one cycle, the reference to such cases written clearly.

In general, test cases should be written in plan simple sentences, referring to Use Cases as and when required with complete traceability for requirements.

Quality Engineers write test cases based on different types of testing. Scope varies from Unit to System to Acceptance test cases. Irrespective of the type, each test case must have its basic characteristics. Happy writing test cases!

(Thank you Rashika, Test Engineer, Aithent Inc for sharing her experiences with test cases.)


Posted on: November 23, 2017 10:25 AM | Permalink

Comments (6)

Please login or join to subscribe to this item
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Thanks for the info on test cases.

avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Thanks for sharing.

avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Does anyone have experience setting up test cases for non-software deliverables, especially services?

avatar
Tiago Romao Project Manager - PfMP | PgMP | PMP | ACP | PBA | CBAP | CSM | MSc.| Altice Portugal | Meo Sobreda, Setubal/Almada, Portugal
Thanks for the tips

I suppose the characteristics of a test case are testers Christmas wishlist :)

Managers, product managers/owners, don't care as much as they should, about the tester perspective. They will write them accordingly to their assumptions, assuming the "audience" will understand.
Test case should be written as SMART as requirements are.

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing

avatar
Karuna Basu New Panvel, Mumbai, Maharashtra, India
Good information about Test Cases. Thanks for sharing !

Please Login/Register to leave a comment.

ADVERTISEMENTS

I don't have a good apartment for an intervention. The furniture, it's very non-confrontational.

- Jerry Seinfeld

ADVERTISEMENT

Sponsors