<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Shashank Gudipati</title>
    <description>The latest articles on DEV Community by Shashank Gudipati (@shashank90).</description>
    <link>https://dev.to/shashank90</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F826778%2Fb27432a5-1361-42db-a1fe-a048988a5106.png</url>
      <title>DEV Community: Shashank Gudipati</title>
      <link>https://dev.to/shashank90</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shashank90"/>
    <language>en</language>
    <item>
      <title>Another API Test Automation tool</title>
      <dc:creator>Shashank Gudipati</dc:creator>
      <pubDate>Wed, 09 Mar 2022 10:26:00 +0000</pubDate>
      <link>https://dev.to/shashank90/another-api-test-automation-tool-58ne</link>
      <guid>https://dev.to/shashank90/another-api-test-automation-tool-58ne</guid>
      <description>&lt;p&gt;As I was writing APIs one day at work, I realized that I wasn't too sure whether those APIs were secure. So I started looking for simple GUI tools that can be used by teams to evaluate their API security posture.&lt;/p&gt;

&lt;p&gt;And in this process I found 3 categories of tools:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Penetration-as-a-service vendors&lt;br&gt;&lt;br&gt;
I wasn't too keen on black-box testing techniques as they come late into the development life-cycle and don't offer much transparency with respect to tests&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Open-source API fuzzers&lt;br&gt;&lt;br&gt;
There are quiet a few robust tools out there. But again these require some time and effort to setup and get going.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Paid tools&lt;br&gt;&lt;br&gt;
Again I could find a bunch of platforms that run 100s of tests but were expensive.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;And so I set forth to writing one by myself. As part of my research, I found out that OpenAPI specification is a good starting point at describing APIs since it's an industry standard and that lot of tooling is available around it.&lt;/p&gt;

&lt;p&gt;Also took the same approach as the other paid and free/open-source tools to finding API security flaws.&lt;/p&gt;

&lt;p&gt;However, I have attempted the following:  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;To keep the UI simple (easy to navigate)&lt;/li&gt;
&lt;li&gt;Maintain OpenAPI Spec validation errors at a minimal so that developers can quickly get documentation out of their way&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Finding Schema validation errors is simple:   &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Upload a spec or Postman Collection or start with a &lt;code&gt;petstore&lt;/code&gt; template&lt;/li&gt;
&lt;li&gt;Fix validation errors and get to a RUN_API status&lt;/li&gt;
&lt;li&gt;Go the Run Tab, select API Endpoint URL and hit Run to find schema validation errors&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Although it's still work in progress, would love for you guys to check it out and share feedback.&lt;/p&gt;

&lt;p&gt;For more information, do check out: &lt;a href="https://cymitra.com"&gt;https://cymitra.com&lt;/a&gt; or head directly to &lt;a href="https://apihome.io"&gt;https://apihome.io&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thank you&lt;/p&gt;

</description>
      <category>security</category>
      <category>api</category>
      <category>testing</category>
      <category>openapi</category>
    </item>
    <item>
      <title>A Simple API Automation Platform </title>
      <dc:creator>Shashank Gudipati</dc:creator>
      <pubDate>Mon, 07 Mar 2022 12:14:50 +0000</pubDate>
      <link>https://dev.to/shashank90/a-simple-api-automation-platform-m61</link>
      <guid>https://dev.to/shashank90/a-simple-api-automation-platform-m61</guid>
      <description>&lt;p&gt;ApiHome is a Simple Test Automation platform.&lt;/p&gt;

&lt;p&gt;We realize that the best way to sanitize API input/output is by describing the API using OpenAPI documentation.&lt;/p&gt;

&lt;p&gt;How does it work? &lt;br&gt;
Upload a spec -&amp;gt; Fix validation errors -&amp;gt; Run API Tests&lt;/p&gt;

&lt;p&gt;Why ApiHome?&lt;/p&gt;

&lt;p&gt;We understand that developers like to get documentation out of their way. So in case you don't have a spec already, feel free to use the default template or a Postman collection to get started&lt;/p&gt;

&lt;p&gt;We have also ensured that Spec validation errors are to the point so developers can quickly fix them &amp;amp; run tests&lt;/p&gt;

&lt;p&gt;Use-cases:  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;API Inventory&lt;/li&gt;
&lt;li&gt;Business-logic testing(corner-cases)&lt;/li&gt;
&lt;li&gt;Security testing&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For more information: Visit &lt;a href="https://cymitra.com/"&gt;https://cymitra.com&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  openapi #api #automation #testing
&lt;/h1&gt;

</description>
      <category>api</category>
      <category>testing</category>
      <category>automation</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
