In this Software Testing Tutorial, we will learn how to write test cases in manual testing of any software testing project. We will learn about test case template and what are key fields in software test case template are a must when writing a test case.
Test case Sheet: docs.google.co...
What is Test Case?
A test case is exactly what it sounds like: a test scenario measuring functionality across a set of actions or conditions to verify the expected result. They apply to any software application, can use manual testing or an automated test, and can make use of test case management tools.
Step 1: Test Case ID
Test cases should all bear unique IDs to represent them. In most cases, following a convention for this naming ID helps with organization, clarity, and understanding.
Step 2: Test Description
This description should detail what unit, feature, or function is being tested or what is being verified.
Step 3: Assumptions and Pre-Conditions
This entails any conditions to be met before test case execution. One example would be requiring a valid Outlook account for a login.
Step 4: Test Data
This relates to the variables and their values in the test case. In the example of an email login, it would be the username and password for the account.
Step 5: Steps to be Executed
These should be easily repeatable steps as executed from the end user’s perspective. For instance, a test case for logging into an email server might include these steps:
- Open email server web page.
- Enter username.
- Enter password.
- Click “Enter” or “Login” button.
Step 6: Expected Result
This indicates the result expected after the test case step execution. Upon entering the right login information, the expected result would be a successful login.
Step 7: Actual Result and Post-Conditions
As compared to the expected result, we can determine the status of the test case. In the case of the email login, the user would either be successfully logged in or not. The post-condition is what happens as a result of the step execution such as being redirected to the email inbox.
Step 8: Pass/Fail
Determining the pass/fail status depends on how the expected result and the actual result compare to each other.
Same result = Pass
Different results = Fail
🔥🔥🔥 One to One connect with Fun Doo Testers : topmate.io/fun...
✅💡 If you like my videos, please consider buying me a coffee: www.buymeacoff...
✅ 💡For business write us on: Contact@fundootesters.com
Topics Covered:
- What is software testing? bit.ly/3xYFIfg
- SDLC Model: bit.ly/3hAwjon
- Waterfall Model: bit.ly/2T6xQsJ
- Prototype Model: bit.ly/3r4ApYV
- Spiral Model: bit.ly/2U6BseT
- V Model: bit.ly/36xXTw0
- Hybrid Model: bit.ly/3wDY0AR
- White box vs Black Box : bit.ly/3izgw8j
- White box Testing: bit.ly/3kBkNLj
- Functional Testing: bit.ly/3zlrs06
- Integration Testing: bit.ly/3rn287r
- System Testing: bit.ly/3zlFdMw
- Smoke Testing: bit.ly/2UVPdgZ
- Adhoc Testing: bit.ly/3zW86PJ
- Regression Testing: bit.ly/3iX3r9e
- Acceptance Testing: bit.ly/3icRaOH
- Compatibility Testing: bit.ly/2VJtSY8
- STLC: bit.ly/37yJaBs
- What is Test Plan: bit.ly/2VKll71
- Defect Life Cycle: bit.ly/3CByIaT
- Test Case Review Process: bit.ly/3fOqkuW
- Severity vs Priority: bit.ly/3jDx53O
-How to create test plan: rb.gy/2ejfc9
-How to write smoke test case : rb.gy/qq31o7
-Web Application testing approach : rb.gy/hqmxsn
-Mobile Application testing : rb.gy/xqlcl3
-How to raise a defect(bug) using google spreadsheet? : rb.gy/zjvoxg
Say hello to us, and stay updated!
✅ Facebook: / fundootesters
✅ Instagram: / fundootesters
✅ LinkedIn: / fundootesters
✅ Blog: fundootesters.com/
GEAR USE:
○ My Camera: amzn.to/3e2UqL7
○ Microphone: amzn.to/3bSUvOq
○ Microphone:amzn.to/2ZXuo3s
○ Tripod: amzn.to/2PqmTQN
DISCLAIMER
Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide I may receive a small commission. There is no additional charge to you! Thank you for supporting me so I can continue to provide you with free content each week!
#testcase #softwaretesting #fundootesters