Scribd
Upload
0 views

Test Cases Template

The document outlines a test case template for a project, detailing sections for project and module information, test scenarios, and various types of tests including positive, negative, edge cases, and security tests. It emphasizes the importance of full coverage in testing using Gherkin syntax, providing examples for each test type and scenario. Additionally, it includes conditions and actions related to specific test cases, ensuring comprehensive validation of the application functionality.

Uploaded by

fihuci
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0 views

Test Cases Template

The document outlines a test case template for a project, detailing sections for project and module information, test scenarios, and various types of tests including positive, negative, edge cases, and security tests. It emphasizes the importance of full coverage in testing using Gherkin syntax, providing examples for each test type and scenario. Additionally, it includes conditions and actions related to specific test cases, ensuring comprehensive validation of the application functionality.

Uploaded by

fihuci
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Test Case Template for Project

Project Name
Module Name
Created By
Created Date
Peer Review By
Peer Reviewed Date

Scenario TIDScenario DesciptionTest Case IDPre Condition


Steps to ExecuteExpected ResultActual ResultStatusExecuted QA Name
Misc (Comments) Pri
Slo Test Type Purpose Example
1 Positive Tests Ensure the happy path works Successful login
2 Negative Tests Handle invalid inputs/errors Wrong password
3 Edge Cases Test boundaries Short password
4 Security Tests Prevent unauthorized access Admin access control
5 Performance Tests Handle heavy loads 100 users logging in
6 Integration Tests Validate API interactions Login API response
7 Error Handling Gracefully recover from failures Database down scenario
8 Regression Tests Ensure old features still work Login after update
9 Accessibility Tests Support disabled users Screen reader support
10 Usability Tests Improve user experience Show password rules
Category
Full Coverage in Gherkin (BDD Testing)
Positive Test Cases

Example - Successful login

Negative Test Cases

Example - Login fails with incorrect password

Edge Cases (Boundary Testing)

Example - Password too short

Example - Password too long

Security and Authorization Checks

Example - Unauthorized user cannot access admin panel

Functional Scenarios

Example - Add an item to the cart

UI/UX Validation

Example - Login button disabled when no credentials are entered

Performance and Load Handling

Example - Handling multiple login attempts

Integration Testing

Example - Login API returns correct response

Error Handling & Recovery

Example - System handles database failure

Regression Testing

Example - Existing user login works after system update

Accessibility Testing
Example - Screen reader support for login page

Usability Testing

Example - Show password requirements during signup

Summary of Full Coverage


Why is Full Coverage Important?
Details
When we say 'full coverage' in Gherkin, it means covering all possible test scenarios for a given functionality.
Ensure that the application works as expected when the user follows the intended flow.
Given the user is on the login page
When the user enters a valid username and password
And clicks on the login button
Then the user should be redirected to the dashboard
Verify that the system handles incorrect or invalid inputs properly.
Given the user is on the login page
When the user enters a valid username but an incorrect password
And clicks on the login button
Then an error message 'Invalid credentials' should be displayed
Tests extreme values to check if the system can handle limits properly.
Given the user is on the registration page
When the user enters 'abc' as a password
Then an error message 'Password must be at least 8 characters long' should be displayed
Given the user is on the registration page
When the user enters a password with 100 characters
Then an error message 'Password cannot exceed 50 characters' should be displayed
Ensuring unauthorized actions are blocked.
Given the user is logged in as a regular user
When they try to access the admin panel
Then an error message 'Access Denied' should be displayed
Verifying core business logic works correctly.
Given the user is on the product page
When the user clicks on 'Add to Cart'
Then the product should appear in the shopping cart
Ensuring elements are displayed correctly.
Given the user is on the login page
When no username and password are entered
Then the 'Login' button should be disabled
Making sure the application functions properly under stress.
Given 100 users are trying to log in simultaneously
When they enter valid credentials
Then the system should authenticate them without crashing
Validating interactions between components or APIs.
Given the user enters valid credentials
When the request is sent to the authentication API
Then the response status should be '200 OK'
And the response should contain 'user_id'
Testing how the system reacts to failures.
Given the database is down
When the user tries to log in
Then an error message 'Service unavailable, please try later' should be displayed
Ensuring old features still work after new updates.
Given the user has a registered account before the update
When they log in using previous credentials
Then they should be redirected to the dashboard
Checking if the application is usable for all users, including those with disabilities.
Given a user with a screen reader visits the login page
When they navigate through the fields
Then all form labels should be read out correctly
Testing how intuitive and user-friendly the system is.
Given the user is on the signup page
When they start typing a password
Then password requirements should be displayed
Covers all major aspects: Positive, Negative, Edge Cases, Security, Performance, Integration, Error Handling, Regression, Acc
Reduces bugs, ensures security, improves user experience, enhances performance, and maintains reliability.
Conditions/Actions TC1 TC2
Condition1 (Account already approved) TRUE TRUE
Condition2 (OTP Matched) TRUE TRUE
Condition3 (Sufficient Money in the Account) TRUE FALSE
Action1 (Transfer Money) Execute
Action2 (Show message 'Insufficient Amount') Execute
Action3 (Block the transaction in case of Suspicious Transaction)
TC3 TC4 TC5
TRUE TRUE FALSE
FALSE FALSE X
TRUE FALSE X

Execute Execute X

You might also like