<?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: Amidat Sule</title>
    <description>The latest articles on DEV Community by Amidat Sule (@amidat_sule_6ba4feb8bcbe2).</description>
    <link>https://dev.to/amidat_sule_6ba4feb8bcbe2</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%2F3576094%2Faf2cc0ba-9700-46aa-ad82-4131bfb216dd.png</url>
      <title>DEV Community: Amidat Sule</title>
      <link>https://dev.to/amidat_sule_6ba4feb8bcbe2</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/amidat_sule_6ba4feb8bcbe2"/>
    <language>en</language>
    <item>
      <title>Stage 3 of the HNGi13 QA Track: API Automation</title>
      <dc:creator>Amidat Sule</dc:creator>
      <pubDate>Tue, 04 Nov 2025 15:42:57 +0000</pubDate>
      <link>https://dev.to/amidat_sule_6ba4feb8bcbe2/stage-3-of-the-hngi13-qa-track-api-automation-132k</link>
      <guid>https://dev.to/amidat_sule_6ba4feb8bcbe2/stage-3-of-the-hngi13-qa-track-api-automation-132k</guid>
      <description>&lt;p&gt;Stage 3 focused on increasing testing skills through comprehensive API testing on the Gradific platform. I explored four main resources: Auth, Users, Workspace, and Workspace Members, executing various requests across positive, negative, and edge case scenarios.&lt;/p&gt;

&lt;p&gt;Using Postman and Newman CLI, I ran structured tests that validated core functionalities such as registration, login, password resets, workspace creation, member tracking, and role updates. Along the way, I encountered several issues, including unexpected status codes, delayed response times, inconsistent handling of invalid or missing inputs, and struggles with Newman report generation. Initially, only CLI outputs were generated, and I had to troubleshoot to export HTML and JSON reports correctly. I also faced challenges with environment variables, particularly with the id variable, which was sometimes not read correctly, causing endpoints to fail or return 404 errors. These challenges highlighted the importance of robust input validation, clear error messaging, and proper API setup.&lt;/p&gt;

&lt;p&gt;Key Learnings&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Proper setup of environment variables and authorization tokens is critical for smooth API testing.&lt;/li&gt;
&lt;li&gt;Edge case testing reveals gaps that are often missed in standard flows.&lt;/li&gt;
&lt;li&gt;Configuring Newman correctly is essential to generate usable reports for review and documentation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;API testing in Stage 3 reinforced that beyond just sending requests, it’s about understanding the communication between systems, predicting potential failures, and ensuring resilience of backend logic.&lt;/p&gt;

&lt;p&gt;QA #SoftwareTesting #Postman #Newman #APITesting #HNGi13 #HNGInternship&lt;/p&gt;

</description>
      <category>api</category>
      <category>automation</category>
      <category>testing</category>
    </item>
    <item>
      <title>Stage 2 of the HNGi13 QA Track: API Testing</title>
      <dc:creator>Amidat Sule</dc:creator>
      <pubDate>Tue, 28 Oct 2025 11:32:50 +0000</pubDate>
      <link>https://dev.to/amidat_sule_6ba4feb8bcbe2/stage-2-of-the-hngi13-qa-track-api-testing-25n9</link>
      <guid>https://dev.to/amidat_sule_6ba4feb8bcbe2/stage-2-of-the-hngi13-qa-track-api-testing-25n9</guid>
      <description>&lt;p&gt;Stage 2 focused on exploring backend quality through API testing using the Gradific platform as a case study.&lt;br&gt;
I tested four core resources: Auth, Users, Workspace, and Workspace Members. Using Postman, I imported the Swagger documentation and organized the endpoints into structured folders for each resource.&lt;br&gt;
I wrote and executed 80 comprehensive test cases, covering positive, negative, and edge scenarios. These validated login flows, workspace creation, user updates, and member role management... ensuring each endpoint behaved as expected.&lt;br&gt;
Along the way, I learned how to handle authorization tokens, set up parameterization and environment variables, and manage protected endpoints effectively. These skills improved my workflow and deepened my understanding of backend logic.&lt;br&gt;
💡 Key Takeaway&lt;br&gt;
API testing isn’t just about sending requests, it’s about understanding how systems communicate. It builds precision, technical intuition, and confidence beyond UI testing.&lt;/p&gt;

&lt;h1&gt;
  
  
  QA #SoftwareTesting #Postman #APITesting #HNGi13 #HNGInternship
&lt;/h1&gt;

</description>
      <category>testing</category>
      <category>api</category>
      <category>learning</category>
      <category>backend</category>
    </item>
    <item>
      <title>Translating Requirements into Test Plan &amp; Strategy: My HNGi13 QA Journey</title>
      <dc:creator>Amidat Sule</dc:creator>
      <pubDate>Wed, 22 Oct 2025 06:08:07 +0000</pubDate>
      <link>https://dev.to/amidat_sule_6ba4feb8bcbe2/translating-requirements-into-test-plan-strategy-my-hngi13-qa-journey-59hc</link>
      <guid>https://dev.to/amidat_sule_6ba4feb8bcbe2/translating-requirements-into-test-plan-strategy-my-hngi13-qa-journey-59hc</guid>
      <description>&lt;p&gt;Stage 1 of the HNGi13 QA Track focused on reviewing requirement documents and translating them into an actionable test plan.&lt;/p&gt;

&lt;p&gt;For this task, I worked on Gradific, a grading and task management platform for educators. My goal was to understand how features like workspace creation, assignment setup, and grading flow together, and then design a testing strategy around them.&lt;/p&gt;

&lt;p&gt;I started by analyzing the PRD and FRD, identifying core functionalities and edge cases. From there, I created a structured Test Plan outlining objectives, scope, approach, risks, and deliverables. I also designed 10 detailed test cases to validate and verify that the requirements are met and the system works as expected. &lt;/p&gt;

&lt;p&gt;This experience taught me how important it is to plan before testing commence, understanding requirements deeply helps uncover gaps early and ensures focused, efficient testing.&lt;/p&gt;

&lt;p&gt;Key Takeaway&lt;br&gt;
Translating requirements strengthens both product understanding and tester intuition.&lt;/p&gt;

&lt;h1&gt;
  
  
  HNGi13 #QA #SoftwareTesting #HNGInternship #TestPlanning #QualityAssurance #BugDetective
&lt;/h1&gt;

</description>
      <category>testing</category>
    </item>
  </channel>
</rss>
