ScriptlessAutomation
  • 👋Welcome to Scriptless Automation
  • Discover More About Automation
    • ⚙️Automation platform intro
    • 💡Advantages of Scriptless Automation
    • 🚀Release Notes
      • 📖Open Code
      • 📕License Code
  • Product tools
    • 📪Pre-request Tools
    • 🔧Project Dependencies
  • Automation Architecture
    • 🎨Flow diagram
  • Get Started
    • 🛠️Start with Automation
    • 📖Open Code Automation
      • 🌏Web Automation
      • ↔️API Automation
    • 🏢Maven Configuration
    • 🗜️Setting Up Maven Project in IntelliJ IDEA
    • 🎛️Scriptless Config
      • 🕸️BrowserConfiguration
        • chrome.properties
      • 👥CommunicationConfiguration
        • SlackConfiguration.properties
      • 📧MailConfiguration
        • gmailCredentials.properties
      • 🛂ReportConfiguration
        • extentReportConfiguration.properties
      • 🕵️TestManagementConfiguration
        • testRail.properties
        • zephyrscale.properties
        • testiny.properties
      • ⚙️testNgConfiguration.properties
    • 🍱TestData Configuration
    • 👨‍💼Gherkin Language and Scriptless Automation Framework
  • Automation Import Notes
    • 🎨Points to Remember
  • Automation Platforms
    • 👾ScriptlessApi Automation
      • 🖊️Introduction
      • 🗜️Api Automation Setup
      • 🔃Supported API Request Types
      • 🪧API Automation Template
      • 📚Example of API Requests
        • ⬇️GET
        • ↕️POST
        • ⤵️PUT
        • ❌DELETE
      • 🎯API Response Validation
      • 👨‍👦API Dependent TestCase
      • 📝Store API Variables
      • 📔API with JSON body
      • 🙋‍♂️Api Wait
      • 🗜️API Schema Validation
      • 🏗️API Tailor-Made coding
      • 👨‍🦯API Support Generator
      • ↘️Api Response Store Objects
      • ✍️API Test Report
      • 🚃Api Response Type Validation
    • 🌐ScriptlessWeb Automation
      • 🖊️Introduction
      • 🗜️Web Automation Setup
      • 🪧Web Automation Template
      • 🧮page_object_locators
      • 📜Web Automation Key Phrases
        • 📃PAGE_NAME
        • ⌛WAIT_TYPE
        • 📜SCROLL_TYPE
        • 👨‍💼ELEMENT_NAME
        • 🏎️ACTIONS
        • ⌨️SEND_KEYS
        • ✔️VALIDATION
        • ✅VALIDATION_TYPE
      • 👨‍👦Web Dependent Test Case
      • 🐒MOCK
      • 🛂AutomationAsserts
      • 🏗️Web Tailor-Made coding
      • 📝Store Web Variables
      • 🤼‍♀️Web & API integration
      • 🖇️Dynamic Strings
      • 🗣️ReadFile Annotation for Custom Code
      • 🖼️Page_Comparison
      • 👨‍💼Gherkin Template for Web Automation
    • 📱Mobile Automation
  • 🪶Automation features
    • 🌲Environment and System Variables
    • 🗝️KeyInitializers
      • Types of KeyInitializers
    • ✍️Reporting
      • Dashboard
      • Category
      • Tests
        • Screenshot Section
    • 👯Parallel Testing
    • 🏗️Tailor-Made Coding
  • ⏩Automation Demo
Powered by GitBook
On this page

Was this helpful?

  1. Automation Platforms
  2. ScriptlessApi Automation
  3. Example of API Requests

DELETE

PreviousPUTNextAPI Response Validation

Last updated 1 year ago

Was this helpful?

Overview

This document serves as a guide for automating a simple DELETE request API without authentication. The API endpoint used in this tutorial ishttps://api-generator.retool.com/7kbSLy/data/53, which is designed to return data for a specified ID.

Automating DELETE Request

Step 1: Importing the cURL command into Postman

The cURL command for the DELETE request is as follows:

curl --location --request DELETE 'https://api-generator.retool.com/7kbSLy/data/53'

Upon importing this cURL into Postman, it translates into an interface with the request and response sections, as seen in the screenshot.

Step 2: Template for Scriptless Automation

To automate the example without writing scripts, the following template can be used:

DEPENDANT_TEST_CASE,NONE,
END_POINT,https://api-generator.retool.com/7kbSLy/data/53,
METHOD,DELETE,
PARAMS:KEY,NONE,
PARAMS:VALUE,NONE,
AUTH:KEY,NONE,
AUTH:VALUE,NONE,
HEADERS:KEY,NONE,
HEADERS:VALUE,NONE,
BODY:KEY,NONE,
BODY:VALUE,NONE,
RESPONSE:CODE,200,
RESPONSE:JSON_PATH,NONE,
RESPONSE:EXPECTED_VALUE,NONE,
RESPONSE:STORE_VALUE,NONE,

This template sets up a test for the DELETE request by specifying the endpoint, method, parameters, and the expected response.

Step 3: Execution and Report Generation

When the test case is executed using the template, the automation tool generates a report that records each step performed during the test. The report includes:

  • The type of request and the endpoint used.

  • The type of request and the response received.

  • Validation of the response code.

Relaxed HTTPS Validation

For environments where HTTPS certificate validation is not required, or in cases where self-signed certificates are in use, the automation tool supports relaxed HTTPS validation. This means the tool will not enforce strict validation of the SSL certificate, allowing the DELETE request to proceed even if the SSL certificate cannot be validated. To use the Relaxed HTTPS for DELETE request change DELETE -> RELAX_DELETE.

Validating the Response

The automation checks for:

  • The HTTP status code, which is expected to be 200.

In this example DELETE request doesn't have the body

👾
📚
❌