SS Nagativecases
Uploaded by
Satish MashaleSS Nagativecases
Uploaded by
Satish MashaleNegative Test Case
Access Issues
Unauthorized Access
Forbidden Access
Expired Tokens
Timeout and Latency
Slow Responses
Timeout Exceeded
Invalid Inputs
Malformed Queries
Incorrect Input Types
Invalid Input Values
Backend Failures
Simulate Downstream API Failure
Database Connection Issues
Rate Limiting
Exceed Rate Limits
Concurrency Issues
Concurrent Requests
Caching Issues
Stale Data
Network Errors
Network Disconnect
Error Handling
Custom Errors
Description
Request without proper authentication
Valid authentication, no permission for resource
Use expired authentication token
Trigger slow response from the server
Send request taking longer than the timeout
Send queries with syntax errors
Provide input values with wrong data types
Test with out-of-range or nonsensical values
Simulate failure in underlying REST API
Simulate database errors or connection issues
Send requests at higher rate than allowed
Send multiple requests simultaneously
Test if cached data is served when outdated
Disconnect network during request
Test scenarios with custom error responses
Expected Outcome
API responds with 401 Unauthorized error and error message indicating unauthorized access.
API responds with 403 Forbidden error and error message indicating access forbidden.
API responds with 401 Unauthorized error and error message indicating token expired.
API responds with a response taking longer than usual.
API responds with 504 Gateway Timeout error or custom timeout error message.
API responds with GraphQL error indicating syntax error.
API responds with GraphQL error indicating input type mismatch.
API responds with GraphQL error indicating invalid input.
API responds with 500 Internal Server Error or custom error message.
API responds with 500 Internal Server Error or custom error message.
API responds with 429 Too Many Requests error indicating rate limiting.
Responses should not intermingle data from different requests and ensure data consistency.
Data should be updated according to caching strategy.
API responds with network-related error codes or messages.
API responds with custom error codes and messages as per error handling logic.
