-
Notifications
You must be signed in to change notification settings - Fork 59
Quality Assurance
Bismita Guha edited this page Aug 30, 2020
·
2 revisions
Currently, all the APIs are being run through common tests to verify their working. You get to view the status codes in your Network tab too.
Possible test cases
| Test Case | Result |
|---|---|
Status Code is 201 or 403 (403 means user already exists, but API working correctly so test case should pass) |
Success |
| Content type header is present | Success |
Status Code 400 & 500
|
Fail |
| Content type header not present | Fail |
Possible test cases
| Test Case | Result |
|---|---|
Status Code is 201 or 200
|
Success |
| Content type header is present | Success |
Status Code 400, 404 & 500
|
Fail |
| Content type header not present | Fail |
Possible test cases
| Test Case | Result |
|---|---|
Status Code is 201 or 200
|
Success |
| Content type header is present | Success |
Status Code 400, 404 & 500
|
Fail |
| Content type header not present | Fail |
Possible test cases
| Test Case | Result |
|---|---|
Status Code is 200
|
Success |
| Content type header is present | Success |
Status Code 400, 404 & 500
|
Fail |
| Content type header not present | Fail |
Possible test cases
| Test Case | Result |
|---|---|
Status Code is 204
|
Success |
| Content type header is present | Success |
Status Code 400, 404 & 500
|
Fail |
| Content type header not present | Fail |
- Home
- AnitaB.org
- About AnitaB.org Open Source
- Getting Started
- How to Contribute
Documentation
- Project Requirements
- Setup and Install
- Development
- Database Design
- Initial Docs
- Main Concepts
- Future Ideas
GSoC Students