Scribd Logo
Upload

Welcome to Scribd!

  • 79 views

    TestCases For ApiTesting

    Uploaded by

    Asjad Siddiqui
    The document outlines API testing test cases to validate GET, POST, PUT, and DELETE requests by checking response codes and response contents, and verifies that requests are processed within expected time frames. It also includes test steps to pass invalid parameters and verify error responses. Expected and actual outputs are recorded for each test case along with any defects observed during testing.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd

    TestCases For ApiTesting

    Uploaded by

    Asjad Siddiqui
    79 views16 pages
    The document outlines API testing test cases to validate GET, POST, PUT, and DELETE requests by checking response codes and response contents, and verifies that requests are processed within expected time frames. It also includes test steps to pass invalid parameters and verify error responses. Expected and actual outputs are recorded for each test case along with any defects observed during testing.

    Original Title

    TestCases for ApiTesting

    Copyright

    © © All Rights Reserved

    Available Formats

    XLSX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines API testing test cases to validate GET, POST, PUT, and DELETE requests by checking response codes and response contents, and verifies that requests are processed within expected time frames. It also includes test steps to pass invalid parameters and verify error responses. Expected and actual outputs are recorded for each test case along with any defects observed during testing.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Download as xlsx, pdf, or txt
    79 views16 pages

    TestCases For ApiTesting

    Uploaded by

    Asjad Siddiqui
    The document outlines API testing test cases to validate GET, POST, PUT, and DELETE requests by checking response codes and response contents, and verifies that requests are processed within expected time frames. It also includes test steps to pass invalid parameters and verify error responses. Expected and actual outputs are recorded for each test case along with any defects observed during testing.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Download as xlsx, pdf, or txt
    You are on page 1of 16
    At a glance
    Powered by AI
    The document provides details about API testing cases including test steps, expected output and actual output.

    The document content has details organized by page number. Each page contains text describing different fields for API testing.

    GET, POST, PUT and DELETE requests are mentioned as different types of API requests to be tested.

    Application Name

    Testing Type

    Browser

    Browser version

    FrontEnd Server Name

    BackEnd Server Name

    DB Name
    <mention application name here> Version

    <manual/automation> Testing Start Date

    <chrome/IE/safari/others> Testing End Date

    <version of the browser on which testing is done> Cycle No.

    <frontend server name on which testing is done> CR Status

    <backend server name on which testing is done> Prepared By

    <DB name on which testing is done> Reviewed By

    Tested By
    <version of the application>

    <testing start date>

    <testing end date>

    <1/2/3>

    <open/close/deferred/hold>
    Case
    Description Menu Name
    No.
    1 Header
    2 Header GET Request
    Observation API Testing

    Observation API Testing


    4

    Observation API Testing

    Observation API Testing

    Observation API Testing

    Observation API Testing

    8 Observation POST Request


    Observation API Testing

    Observation API Testing


    10
    Observation API Testing

    11

    Observation API Testing

    12

    Observation API Testing

    13

    14 Observation PUT Request


    Observation API Testing

    15

    Observation API Testing


    16

    Observation API Testing

    17

    Observation API Testing

    18

    19 Observation DELETE Request


    Observation API Testing
    20

    Observation API Testing


    21
    Observation API Testing

    22

    Observation API Testing

    23

    24 End of File
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75 End of File
    Test Cases Test Steps Test Data
    API Testing Test Cases

    Verify by sending "GET" request after filling


    necessary details for the following:
    01. Authorization
    02. HTTP Headers
    03. Filter Params

    Check for the response status code recieved for


    the "GET" request.
    Verfy the Array Details recieved in response for
    the "GET" request.

    Verify the Array Details received in response for


    the "GET" request.

    Check for the time taken for fetching the


    response of "GET" request.

    Check by passing Invalid parameters in Request.

    Verify by sending "POST" request after filling


    necessary details for the following:
    01. Authorization
    02. HTTP Headers
    03. Request Body

    Check for the response status code received for


    the "POST" request.
    Check for the Auth Token received in response.

    <This case will be tested in case of login Post


    request>

    Check for the time taken for fetching the


    response of "POST" request.

    Check by passing following values in Request:


    01. Mandatory field left blank
    02. Invalid Values passed.

    Verify by sending "PUT" request after filling


    necessary details for the following:
    01. Authorization
    02. HTTP Headers
    03. Request Body

    Check for the response status code recieved for


    the "PUT" request.
    Check for the time taken for fetching the reposne
    of "PUT" request.

    Check by passing following values in Request:


    01. Mandatory field left blank
    02. Invalid Values passed.

    Verify by sending "DELETE" request after filling


    necessary details for the following:
    01. Authorization

    Check for the response status code recieved for


    the "PUT" request.
    Check for the time taken for fetching the reposne
    of "POST" request.

    Check by passing following values in Request:


    01. Invalid value passed in header.
    Cycle 1
    Description of actual
    Expected Output Actual Output
    defect

    System shoud send the "GET" request


    successfully.

    Response Code "200" should be recieved.

    Array count should be greater than Zero in


    response, else it should have appropriate
    message if no records exists.

    Following details should be received in


    response :

    <Mention the Data you want to verify with


    their respective values>

    System should receive the response in


    minimal time.
    <Approximately response should be
    received within 1-3 seconds>

    System should not fetch response


    successfully.
    01. Response Code should be not in range
    of 2xx.
    02. Error should be received in response.

    System should send the "POST" request


    successfully.

    Response Code "200"/"201" should be


    received.
    System should generate fresh token in
    response.
    Token value should not be null.

    System should receive the response in


    minimal time.
    <Approximately response should be
    received within 1-3 seconds>

    System should not fetch response


    successfully.
    01. Response Code should be not in range
    of 2xx.
    02. Error should be received in response.

    System shoud send the "PUT" request


    successfully.

    Response Code "200"/"201" should be


    recieved.
    System should receive the reponse in
    minimal time.
    <Approximately response should be
    received within 1-3 seconds>

    System should not fetch response


    successfully.
    01. Response Code should be not in range
    of 2xx.
    02. Error should be received in response.

    System shoud send the "DELETE" request


    successfully.

    Response Code "200" should be recieved.


    System should receive the reponse in
    minimal time.
    <Approximately response should be
    received within 1-3 seconds>

    System should not fetch response


    successfully.
    01. Response Code should be not in range
    of 2xx.
    02. Error should be received in response.
    e1 Cycle 2
    Description of actual
    Defect ID Actual Output Defect ID
    defect
    Cycle 1 - Test Summary

    Correct
    Incorrect
    Suggestion
    Can't Test
    Cycle 1 - Test Summary

    0
    0
    0
    0

    You might also like