- This topic has 3 replies, 4 voices, and was last updated 6 years, 12 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › Software Testing Discussions › Effective Test Case Design
What are the principles you follow to create effective test cases in your work place?
Please comment with the type of application you work with along with the principles you follow
Test Case is a part of Software Testing. Software testing is procedure of finding an error or bug either manually or with the use of automation tools.
some principles for effective test case:
1. Exhaustive Testing is not possible
2. Defect Clustering
3. Testing will show presence of defects
4. early testing
[commercial content removed /mod]
@Darwin. Test cases should be written during the earlier stage of the software development life cycle. Gathering software requirement is the best phase to write the test case. Testers should have to follow these points for effective test cases which can also increase the efficiency of those test cases:
– Detailed requirements specified by the Customer
– Keep a track of all used cases
– Requirements based on functionality in detail
– Project Plan of Application to be created
– Brief documentation of the project milestones
To read more about how to create test cases proficiently, this blog helps a lot in clearly digging the things deeper: https://www.bugraptors.com/improve-test-case-efficiency/
[reviewed by mod, link ok /JO]
Munish Sharma