<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Santhosh Selladurai on Medium]]></title>
        <description><![CDATA[Stories by Santhosh Selladurai on Medium]]></description>
        <link>https://medium.com/@sandykumaru?source=rss-6b73178d4afc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OEtX4GOJDMmvRIoG5BNn7Q.jpeg</url>
            <title>Stories by Santhosh Selladurai on Medium</title>
            <link>https://medium.com/@sandykumaru?source=rss-6b73178d4afc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:23:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sandykumaru/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Add Power to Your TestRail Test Cases with DevAssure]]></title>
            <link>https://medium.com/@sandykumaru/add-power-to-your-testrail-test-cases-with-devassure-ad9ca2fc6a1a?source=rss-6b73178d4afc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad9ca2fc6a1a</guid>
            <category><![CDATA[agentic-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[browser-automation]]></category>
            <category><![CDATA[web-ui-testing]]></category>
            <category><![CDATA[testrail]]></category>
            <dc:creator><![CDATA[Santhosh Selladurai]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 06:53:00 GMT</pubDate>
            <atom:updated>2026-06-03T06:53:00.844Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vkc7gRxW8y1BxIU9NZEZbQ.png" /></figure><p>Your team already plans and tracks tests in <a href="https://www.testrail.com/">TestRail</a>. The gap is execution: turning those cases into reliable UI automation without a second script suite to maintain. <strong>DevAssure closes that loop</strong> — fetch cases from TestRail, run them in a real browser with an AI agent, and optionally sync results, defects, and videos back to TestRail.</p><p>Every TestRail workflow in this guide is available in <strong>two places</strong>: the <a href="https://www.npmjs.com/package/@devassure/cli">@devassure/cli</a> for terminals and CI/CD, and the <strong>DevAssure VS Code extension (VSCE)</strong> for interactive runs from the IDE. Configure once—credentials and post-result settings are shared between both.</p><h3>Introduction: Why TestRail matters</h3><p><a href="https://www.testrail.com/">TestRail</a> is a widely adopted test management platform built for QA teams who need a single place to organize test cases, plan execution, track results, and report on quality. Instead of scattering cases across spreadsheets or wikis, teams use TestRail’s structured repository — projects, suites, sections, cases, runs, and milestones — to keep manual and automated testing aligned with releases.</p><p>For software teams, TestRail delivers:</p><ul><li><strong>Centralize test strategy</strong> — Manual, automated, and exploratory work lives in one hub with clear workflows.</li><li><strong>Plan and execute efficiently</strong> — Test runs, plans, and milestones organize work by sprint or release.</li><li><strong>Improve visibility</strong> — Dashboards and reports surface coverage, failures, and bottlenecks for engineering and product leaders.</li><li><strong>Integrate with your stack</strong> — Native connections to Jira, CI/CD, automation frameworks, and a full <a href="https://www.gurock.com/testrail/docs/api/reference/">REST API</a> for custom automation.</li></ul><p>More on <a href="https://www.testrail.com/test-management-for-software-teams/">TestRail for software teams</a>.</p><p>TestRail also supports traceability (linking requirements, cases, and defects) and enterprise controls such as role-based access and audit trails — making it a strong system of record for <em>what</em> to test and <em>what happened</em> during execution.</p><p>The gap many teams still feel is on the <strong>execution</strong> side: turning well-written TestRail cases into reliable, up-to-date UI automation without maintaining brittle scripts. That is where DevAssure fits in.</p><h3>DevAssure: Execute TestRail cases with an AI testing agent</h3><p><a href="https://www.devassure.io/">DevAssure</a> is an AI-powered testing platform centered on <strong>DevAssure O2</strong> — an agent that understands your application, executes tests in a real browser, and adapts when the UI changes. You describe steps in <strong>plain English</strong> (or manage them in TestRail); DevAssure interprets intent and runs the flow — no traditional test scripts required.</p><p>Key benefits for teams already using TestRail:</p><ul><li><strong>Scriptless execution: </strong>TestRail steps written in natural language can be run directly by the DevAssure agent.</li><li><strong>Real browser validation: </strong>End-to-end checks run against Chromium, Chrome, or Edge with configurable headless/headed modes.</li><li><strong>Closed loop with TestRail: </strong>Fetch cases from TestRail, execute them, then optionally post results, log defects, and attach session videos back to TestRail runs.</li><li><strong>CLI and VSCE workflows: </strong>Run TestRail cases from the CLI in CI/CD or from the <a href="https://marketplace.visualstudio.com/items?itemName=DevAssure.devassure-agent-vscode-extension">VS Code extension (VSCE)</a> in the IDE — same provider config, filters, and post-result options.</li><li><strong>PR-native testing (O2): </strong>For code-change workflows, O2 maps blast radius and generates or updates checks — complementary to your TestRail catalog.</li></ul><p>Learn more at <a href="https://www.devassure.io/o2-testing-agent">DevAssure O2</a>.</p><p>DevAssure treats TestRail as a <strong>test provider</strong>: an external source from which cases are fetched, executed, and — when configured — reported back automatically.</p><h3>Prerequisites</h3><p>Before connecting TestRail, ensure you have:</p><ul><li>A <strong>DevAssure account</strong> — <a href="https://app.devassure.io/sign_up">Sign up</a> (free trial available)</li><li><strong>TestRail API access</strong> — Your TestRail URL, username, and <a href="https://www.gurock.com/testrail/docs/api/getting-started/accessing/">API key</a> (Administration → Site Settings → API in TestRail)</li><li><strong>DevAssure CLI or VSCE installed and signed in</strong> — Install the <a href="https://www.npmjs.com/package/@devassure/cli">@devassure/cli</a> (npm install -g @devassure/cli) or the <a href="https://marketplace.visualstudio.com/items?itemName=DevAssure.devassure-agent-vscode-extension">DevAssure VS Code extension (VSCE)</a>, then sign in with devassure login or from the extension sidebar</li><li><strong>Add test data (optional)</strong> — Initialize .devassure by running devassure init command and include any data like credentials in .devassure/test_data.yaml file. Reference documentation - <a href="https://www.devassure.io/docs/DevAssure/Invisible%20Agent/CLI/overview/#initialize-your-project">Initialize and add test data</a></li></ul><h3>How to configure TestRail in DevAssure</h3><p>DevAssure stores TestRail credentials in an <strong>encrypted</strong> file: &lt;secrets-directory&gt;/testrail.enc.json. Credentials are never written to your repo in plain text. You can add and update this config from the <strong>CLI</strong> or <strong>VSCE</strong>—both write to the same file.</p><h3>Add provider config</h3><p><strong>CLI — interactive setup</strong> (recommended the first time):</p><pre>devassure add-provider-config</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BElDWcMOibPTKh-s.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qzLOZKXkcdWSBG1_.png" /></figure><p>When prompted, choose provider <strong>testrail</strong> and enter:</p><p><strong>URL </strong>Your TestRail instance, e.g. <a href="https://yourcompany.testrail.io/">https://yourcompany.testrail.io</a></p><p><strong>Username </strong>TestRail user email or username</p><p><strong>API key</strong>TestRail API key</p><p><strong>Project ID (</strong>Optional) leave empty if your account has only one project</p><p><strong>CLI — non-interactive setup</strong> (CI or scripting):</p><pre>devassure add-provider-config \<br>  --provider testrail \<br>  --url https://yourcompany.testrail.io \<br>  --username qa-user@company.com \<br>  --api-key YOUR_API_KEY \<br>  --project-id 42</pre><p><strong>VSCE — equivalent steps</strong></p><ol><li>Open the DevAssure <strong>Configuration</strong> view in the sidebar.</li><li>Click <strong>DevAssure: Add Provider Config</strong> in the view title bar, or run the command from the Command Palette.</li><li>Select <strong>testrail</strong> if prompted.</li><li>Enter URL, username, API key, and optional project ID.</li></ol><h3>Configure how results are posted back (recommended before first run)</h3><p>Before running TestRail cases, decide whether DevAssure should update TestRail after execution. The same options are available in <strong>CLI flags</strong> and <strong>VSCE settings</strong>.</p><p><strong>VSCE — Command Palette</strong></p><p>Run <strong>DevAssure: TestRail post result settings</strong> (devassure.testRailPostResultSettings) to configure:</p><ul><li><strong>Post results to TestRail</strong> — on/off</li><li><strong>Log defects to TestRail</strong> — on/off (only when post results is enabled)</li><li><strong>Attach videos to TestRail</strong> — Never, On-Failure, or Always (only when post results is enabled)</li></ul><p><strong>VSCE — Workspace settings</strong></p><ul><li>devassure.testrail.postResults (boolean)Create/update TestRail run results after execution</li><li>devassure.testrail.logDefects (boolean)Log defects for issues found during the run</li><li>devassure.testrail.attachVideos never | on-failure | always</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EIPvH0PM-GJuWeaK.png" /></figure><p><strong>CLI equivalents</strong> (used with --provider testrail):</p><ul><li>--post-results — Post execution results to TestRail</li><li>--log-defects — Requires --post-results; enables defect logging (--add-defects on the agent)</li><li>--attach-videos &lt;mode&gt; — Requires --post-results; never, on-failure, or always</li></ul><p>Example combining all three on a run:</p><pre>devassure run --provider testrail \<br>  --labels=smoke \<br>  --post-results \<br>  --log-defects \<br>  --attach-videos=on-failure</pre><h3>How to run TestRail cases from DevAssure</h3><p>Once TestRail is configured, DevAssure <strong>fetches cases from TestRail</strong> instead of local YAML/CSV.</p><p>Use <strong>devassure run</strong> in the CLI, or <strong>Run TestRail cases</strong> / <strong>Run TestRail cases by id</strong> in the VSCE <strong>Tests</strong> view—the same filters apply in both.</p><h3>Run by section, labels and priority</h3><p><strong>CLI:</strong></p><pre>devassure run --provider testrail \<br>  --section=user_management \<br>  --labels=smoke,regression \<br>  --priority=P0 \<br>  --post-results</pre><p><strong>VSCE:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-gUWXEe9L45gD09k.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*49YvAsk2VdWAYH-R.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9gx_K-ayanUs5ZMB.png" /></figure><h3>Run by project and case IDs</h3><p><strong>CLI:</strong></p><pre>devassure run --provider testrail \<br>  --project-id=42 \<br>  --case-ids=1001,1002 \<br>  --post-results</pre><h3>Run by section with defects and videos on failure</h3><p><strong>CLI:</strong></p><pre>devassure run --provider testrail \<br>  --filter=&quot;section=Regression &amp;&amp; priority=P0&quot; \<br>  --post-results \<br>  --log-defects \<br>  --attach-videos=on-failure</pre><p><strong>Structured filter flags</strong></p><ul><li>--provider testrail Fetch cases from TestRail</li><li>--project-id TestRail project ID</li><li>--suite-id Suite ID (multi-suite projects)</li><li>--section Section name</li><li>--labels Comma-separated labels</li><li>--priority Comma-separated priorities</li><li>--case-ids Comma-separated case IDs (other filters are ignored)</li></ul><p><strong>CLI:</strong></p><pre>devassure run --provider testrail \<br>  --filter=&quot;labels=smoke,regression &amp;&amp; priority=P0&quot; \<br>  --post-results</pre><h3>VSCE: Run from the Tests view</h3><p>After configuration, the <strong>Tests</strong> view shows:</p><ol><li><strong>Run TestRail cases</strong> — Pick project (if not saved), suite (for multi-suite projects), then optional section, priority, and labels.</li><li><strong>Run TestRail cases by id</strong> — Enter comma-separated case IDs.</li></ol><p>Execution logs appear in <strong>Run Logs</strong>, same as local YAML/CSV runs.</p><h3>CI/CD example (CLI)</h3><pre>devassure add-token &quot;$DEVASSURE_TOKEN&quot;<br>devassure run --provider testrail \<br>  --labels=smoke \<br>  --post-results \<br>  --attach-videos=on-failure \<br>  --archive=./test-reports<br>devassure summary --last --json</pre><h3>How results are posted back to TestRail</h3><p>When <strong>--post-results</strong> (or devassure.testrail.postResults) is enabled, DevAssure syncs execution outcomes to TestRail automatically:</p><p><strong>A TestRail run is created</strong> for the session, and every executed test case is <strong>attached to that run</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lT0GJgYH1E7lCCVo.png" /></figure><p><strong>A result is posted for each test</strong> — pass, fail, or blocked — so individual case status is recorded in TestRail without manual entry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4xW4cz8RLHnJ5VX3.png" /></figure><p><strong>Execution summaries are added at both levels</strong> — each test result includes a summary of what happened during that case, and the run itself gets an overall <strong>execution summary and score</strong> (pass/fail counts and run-level metrics) so dashboards and reports reflect the full session at a glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gEN45g2X2bPlJNld.png" /></figure><p>Your TestRail dashboards and reports stay current as soon as DevAssure finishes executing.</p><h3>Defects created in TestRail</h3><p>Enable <strong>--log-defects</strong> (CLI) or <strong>Log defects to TestRail</strong> (VSCE) together with post results.</p><p>When the DevAssure agent finds a bug during execution, it can <strong>log a defect in TestRail</strong> linked to the failing case — giving testers and developers a traceable record inside the same tool they already use for test management. This maps to the agent flag --add-defects and requires both --post-results and --provider testrail.</p><p>Typical workflow:</p><ol><li>A TestRail case fails during DevAssure execution.</li><li>With defect logging on, DevAssure creates a TestRail defect with context from the failure.</li><li>Your team triages the defect in TestRail (and can link to Jira or other integrations TestRail already supports).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*55dAXyfzsGAAAaDU.png" /></figure><h3>Video attachments for reference</h3><p>Session recordings help reproduce failures without re-running locally. Enable video attachment with <strong>--attach-videos</strong> in the CLI or <strong>Attach videos to TestRail</strong> in VSCE post result settings.</p><ul><li>never Do not attach videos (default)</li><li>on-failure Attach video when a case fails</li><li>always Attach video for every case</li></ul><p>Videos are attached to the TestRail run when results are posted, giving reviewers a <strong>visual record of what the browser did</strong> — clicks, navigation, and UI state at failure time.</p><p><strong>CLI:</strong></p><pre>devassure run --provider testrail \<br>  --case-ids=1001,1002 \<br>  --post-results \<br>  --attach-videos=on-failure</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/0*62oPzEcmS6MgZ6Ho.png" /></figure><h3>End-to-end workflow at a glance</h3><pre>TestRail cases<br>      │<br>      │  Fetch via API<br>      ▼<br>   DevAssure ──► AI agent executes in browser ──► Pass / Fail<br>                                                      │<br>                    ┌─────────────────────────────────┼──────────────────────────────┐<br>                    │                                 │                              │<br>           (optional) post-results           (optional) log-defects         (optional) attach-videos<br>                    ▼                                 ▼                              ▼<br>           TestRail run updated               TestRail defect                   Video on result<br>           (+ run summary &amp; score)            (linked to failing case)          (on test result)</pre><ol><li><strong>Author and organize</strong> cases in TestRail (sections, priorities, labels).</li><li><strong>Configure</strong> TestRail credentials once in DevAssure — via CLI or VSCE.</li><li><strong>Run</strong> selected cases via CLI, VSCE, or CI.</li><li><strong>Review</strong> DevAssure reports locally; <strong>sync</strong> outcomes to TestRail when post settings are enabled.</li><li><strong>Triage</strong> defects and watch session videos directly in TestRail.</li></ol><h3>Tips for a smooth integration</h3><ul><li><strong>Write executable steps in TestRail</strong> — Natural-language steps work best when they are action-oriented (“Log in as admin”, “Verify dashboard shows welcome message”).</li><li><strong>Keep project ID in config</strong> for multi-project accounts to skip project selection prompts.</li><li><strong>Use </strong><strong>--suite-id</strong> when your TestRail project uses multiple suites (suite_mode = multiple).</li><li><strong>Start with </strong><strong>--attach-videos=on-failure</strong> to balance storage and debuggability.</li><li><strong>Align environments</strong> — Use devassure init test data (test_data.yaml) and --environment so URLs and credentials match the target under test.</li></ul><h3>Summary</h3><p>TestRail remains the <strong>system of record</strong> for what to test and how releases are tracked. DevAssure adds <strong>execution power</strong> from the CLI or VSCE: run those same cases in a real browser with an AI agent, optionally <strong>post results</strong>, <strong>log defects</strong>, and <strong>attach videos</strong> — so your TestRail investment extends from planning into fast, maintainable automation without maintaining a separate script suite.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad9ca2fc6a1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 tools and techniques that full-stack software testers should know]]></title>
            <link>https://medium.com/@sandykumaru/15-tools-and-techniques-that-full-stack-software-testers-should-know-d34caf86f37?source=rss-6b73178d4afc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d34caf86f37</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[testing-techniques]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Santhosh Selladurai]]></dc:creator>
            <pubDate>Mon, 06 Dec 2021 10:33:17 GMT</pubDate>
            <atom:updated>2021-12-06T10:33:17.421Z</atom:updated>
            <content:encoded><![CDATA[<h4>List of some testing techniques and tools that every test engineer should be familiar with, that help you to grow into a full-stack quality engineer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*GxgZqT9EXhLgsMgSJH1uqQ.jpeg" /></figure><p>Application testing is a very vast domain involving testing of multiple components and different aspects of the software. With “shift left testing” movement, various aspects of testing are moved to the early stages of development lifecycle. Unlike earlier times where there were experts for each type of testing, QA engineers are expected to be end to end experts or “Full stack test engineers”. Here are some of the type of tools that will help you in the end to end testing of various application components.</p><p><em>The tools suggested are my personal choices and there could be better tools available.</em></p><h4>1. <strong>Device farm for cross browser / device testing</strong></h4><p>Web, mobile and desktop applications need to be tested in different browsers, operating systems and devices, in different versions to make sure that there are no bugs in specific device or version. Buying and maintaining the devices is a costly process and you could never keep up with the number of devices being released in the market daily. Device farms help us achieve this. You can choose the device farm provider based on the type of platforms you support - web, mobile, desktop or multiple platforms.</p><p>Tools - BrowserStack, LambdaTest, pCloudy, SauceLabs, AWS Device farm.</p><h4>2. <strong>Testing the network traffic of the application</strong></h4><p>All popular browsers’ dev tools network gives a good view of the network calls made from your application and the timeline view as well. Use this effectively to identify the unwanted calls made or wrong parameters passed to an API. This also helps you to identify the slow apis that is affecting your app’s performance. This is the first step in testing performance in the early stages of the development lifecycle.</p><p>Tools - Developer tools of Browsers</p><h4>3. <strong>API Testing</strong></h4><p>You need not be an API testing expert to identify basic bugs in the APIs. Use basic tools like Postman to test your API with different data to uncover multiple types of issues.</p><p><strong>Functional</strong> - If the API is returning the right data.</p><p><strong>Security</strong> - Changing the parameters should not give the data that user doesn’t have access to.</p><p><strong>Performance </strong>- There could be bugs like API returning thousands of records without pagination.</p><p>Tools - Postman</p><h4>4. <strong>Email testing</strong></h4><p>There are n number of email clients across different platforms (mobile, desktop, web), the mail you send to the users should support all the clients in all screen sizes. Keep an eye on the <strong>Dark mode</strong> of email client also. There are tools that make testing on multiple email clients easy.</p><p>Tools - Email on Acid, Litmus, MailTrap.</p><h4>5. <strong>Temporary email addresses</strong></h4><p>If you need multiple emails to test in your application, there are tools that give you temporary emails for testing. This comes in handy especially when your application doesn’t support + in email addresses.</p><p>Tools - Emailfake.com, fakemailgenerator.com, generator.email.</p><h4>6. <strong>Screen capture / recording</strong></h4><p>Key part of bug tracking is knowing the exact ways to reproduce a bug. Adding a screenshot or screen recording is an easy way to explain a bug. Using a cloud based tools gives an easy way to share the recoding as a link easily.</p><p>Tools - CloudApp, Loom.</p><p>There are few unique tools like Tango.us that creates a step-by-step guide.</p><h4>7. <strong>Session manager extensions for browsers</strong></h4><p>Session managers help you use your website in multiple tabs/windows each with a different login simultaneously. This will remove your huge effort of having to log-out and log-in to switching over to multiple users while testing. Some of the popular extensions are</p><p>Chrome extensions - Tab Session Manager, Session Box, Session Buddy</p><p>Firefox extensions - Firefox Multi-Account Containers, Session Box</p><h4>8. <strong>Font checker</strong></h4><p>Sometimes it is hard to tell two fonts apart. There are browser extensions to easily show the fonts used in your website. You can identify the bugs in fonts or styles used. Some of the popular extensions are</p><p>Chrome extensions - Fonts Ninja, Font finder, WhatFont</p><p>Firefox extensions - Fonts Ninja, Font Finder</p><h4>9. <strong>Cookie managers</strong></h4><p>Play around with your site cookies to see how your site behaves when a cookie is altered or removed. Browser dev tools have these capabilities, but there are extensions that are easier to use. Many sites store some user preferences in cookies, editing/removing them can open up new types of bugs. Popular extensions</p><p>Chrome extensions - CookieManager - Cookie Editor, EditThisCookie</p><p>Firefox extensions - CookieEditor, EditThisCookie2</p><h4>10. <strong>Device resource monitoring</strong></h4><p>Your web page, mobile or desktop applications can consume a lot of the device resources that you know. The important things to monitor are CPU, Memory, Battery. If your mobile or desktop application is running as a background service, it is more important to test the resource consumption.</p><p><strong>For websites, </strong>Chrome DevTools has the performance tab that allows us to record the memory usage of the website. Safari - the macOs Activity Monitor allows you to monitor the tabs opened in Safari. Firefox -</p><p><strong>For Mobile device, </strong>there are multiple apps in the stores for monitoring CPU, Memory, Battery of the device and the consumption by each app.</p><h4>11. Security testing</h4><p>Security testing has a vast scope. There are different types of security testing or assessments. As an application tester, you can do basic security validations.</p><ul><li>Check if your application is resistant to denial of service attacks. Run scripts to hit your application urls or apis continuously from a machine outside your trusted network and validate if you are being rate limited.</li><li>Common attacks on your systems are done due to unwanted ports that are open. Run a scan on your endpoints to discover the ports that are vulnerable. Tools like Burp include an engine that can crawl your web apps and find a wide range of vulnerabilities.</li><li>Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into websites and making the application vulnerable to session hijacking, data breach or even modify the site content. You can try adding scripts in all the input fields and validate how it is handled. Or use tools that can scan the fields vulnerable to XSS attack.</li></ul><p>Tools — OWASP ZAP</p><h4>12. <strong>Accessibility testing</strong></h4><p>Accessibility testing usually is done as a separate cycle, but most of the accessibility issues can be captured early in the lifecycle with the help of some tools. Minor issues like un-accessible actions, contrasts, aria can be identified early in the cycle.</p><p>Test your application with voice over and zoom options provided by the OS.</p><p>Chrome and Firefox extensions - Axe devTools, Wave, SiteImprove, Accessibility Insights for Web.</p><h4>13. Data <strong>Simulation (Location, Call, SMS)</strong></h4><p>Applications involving services like Location, Calls, SMS or even some third party API calls, are sometimes hard to test. Use tools to simulate those services. Tools like VPN, fake GPS, fake call, fake SMS, API mocking tools help you simulate real world scenarios with ease.</p><h4>14. <strong>API failures simulation</strong></h4><p>Applications consume a lot of third party APIs to achieve few things. We often fail to test how our application behaves when one or more of these APIs fail. There are multiple reasons for the failure, user’s AD blockers can block it, the firewall of user’s network can block many urls. To identify those,</p><p>Use different <strong>Ad blockers</strong> with different settings to identify all the APIs blocked and how the app handles it</p><p>To block individual APIs and test the application behaviour <strong>browser DevTools</strong> have those abilities or use a <strong>mocking tool </strong>to simulate different failures.</p><p>Simulating a slow network or simulating various API response codes should be done for your application APIs as well.</p><h4>15. <strong>Auto Form filler</strong></h4><p>Auto form fill extensions allow you to quickly enter details. This would be handy when testing length forms. You can either use extensions that fill in random values or save the predefined values and use it every time. These extensions not only reduce your time, but also capture the bugs when a field accepts an input that it is not supposed to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d34caf86f37" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>