<?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 Sanjeev Chevireddy on Medium]]></title>
        <description><![CDATA[Stories by Sanjeev Chevireddy on Medium]]></description>
        <link>https://medium.com/@sanjeev.chevireddy?source=rss-bb4bb57b2841------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Sanjeev Chevireddy on Medium</title>
            <link>https://medium.com/@sanjeev.chevireddy?source=rss-bb4bb57b2841------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:59:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sanjeev.chevireddy/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[Automation on the Fly: Writing Custom Tests Using Our Automation Framework]]></title>
            <link>https://blog.enable.engineering/automation-on-the-fly-writing-custom-tests-using-our-automation-framework-f05dac632986?source=rss-bb4bb57b2841------2</link>
            <guid isPermaLink="false">https://medium.com/p/f05dac632986</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Sanjeev Chevireddy]]></dc:creator>
            <pubDate>Tue, 10 Dec 2024 13:52:46 GMT</pubDate>
            <atom:updated>2024-12-10T13:52:46.446Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Innovating QA at Enable: Empowering Developers with Automation</strong></p><p>At Enable, our QA team is dedicated to aligning with the fast-paced nature of our development cycle while upholding top-tier product quality. One of our primary challenges has been providing capabilities to support multiple products built on a diverse technology ecosystem. This includes testing across multiple front-end frameworks like Knockout.js, Angular and Blazor, traditional back-end architecture such as RestAPIs and SQL Server and modern solutions using GraphQL, Cosmos DB and Databricks. This technological diversity made developing a consistent and thorough test coverage approach across all layers of our applications challenging.</p><p>As Enable grows its QA function, we currently face a notable development to QA ratio. This imbalance places significant pressure on the QA team to ensure comprehensive testing within tight timeframes, often making traditional testing methodologies insufficient. These challenges underscored the urgent need for an efficient and scalable approach to test automation.</p><p>To address this, we strategically selected tools tailored to our technology stack, Playwright is a modern and comprehensive front-end testing tool, we utilise RestSharp library to cover our RestAPI and utilise a variety of libraries to cover tests in back-end services e.g. GraphQL, HTTP, Databricks, Cosmos and SQL clients for container and database validation. Our framework is wrapped and published as a NuGet package so that QA and Engineer teams can use the relevant utilities in their project repositories, ensuring seamless integration with our development practices.</p><p>This framework bridged the gap between development and QA responsibilities, enabling developers to actively contribute to test creation. This approach not only streamlined testing but also fostered a culture of shared ownership in quality assurance. By integrating automation at every level, we reduced testing bottlenecks, enhanced early bug detection, and improved overall code reliability.</p><p>This article delves into how Enable overcame these challenges by leveraging a unified toolset, fostering collaboration, and embracing an agile approach to test automation. Our journey demonstrates the impact of empowering both QA and development teams to meet the demands of a dynamic and fast-paced development environment.</p><p><strong>Why Enable Opted for Developer-Driven Automation</strong></p><p>As Enable’s product offerings expanded, so did our backlog of testing and automation needs. Depending solely on our dedicated QA team for exhaustive coverage led to bottlenecks, particularly when development teams were rapidly iterating on new features. To address the inherent constraints of a limited QA to developer ratio, we championed a strategy that encouraged developers to incorporate testing within their workflow through an accessible, shared automation framework.</p><p>By adopting this developer-driven approach, our team detected and resolved critical issues earlier in the development cycle. Previously, most defects surfaced during end-stage regression testing or, worse, after deployment. With developers conducting feature-specific tests upfront, we now catch potential issues at the source before they escalate.</p><p><strong>Creating the Automation Framework</strong></p><p>At Enable, our automation framework has to be built to address the complexity of our various technology stacks, while ensuring a seamless and repeatable testing experience for our engineers. It is designed to be intuitive, adaptable, and capable of supporting robust validation at every layer of our applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PS6QbsTOVeFSNsyrQ2K4vA.png" /></figure><p><strong>Why We Chose Specific Tools</strong></p><p>At Enable we are a .Net first engineering team, so we look to leverage tools that support C# natively.</p><ol><li><strong>Playwright for Front End Validation</strong><br><a href="https://playwright.dev/dotnet/">Playwright</a> provides a powerful and versatile solution for end-to-end testing of user interfaces across multiple front-end technologies, it supports any web front-end actions such as interaction with Angular and Blazor sites. Its cross-browser compatibility ensures consistent testing, while its rich API allows us to simulate real-world user interactions, such as mouse clicks, drag-and-drop actions, and network conditions. This enables our QA engineers and developers to validate user journeys efficiently and reliably.</li><li><strong>Backend Clients for Database Validation</strong><br>Libraries like Cosmos, HTTP and SQL clients enable direct and precise validation the back-end data states. of our application. As we deal with many calculations and verifications in our products, we have to ensure the integrity and consistency of data across various layers, from transaction processing to data retrieval. These libraries also help validate scenarios where database operations influence critical application workflows.</li><li><strong>RestSharp for API Validation</strong><br>For API validation, <a href="https://restsharp.dev/">RestSharp</a> simplifies the process of sending requests and validating responses. This ensures that APIs adhere to expected behaviours e.g. correct status codes, and data consistency across systems like Databricks and Cosmos DB and error handling. It’s particularly beneficial for testing complex integrations and workflows where APIs act as the bridge between different components.</li></ol><p><strong>Key Benefits of the Framework</strong></p><ol><li><strong>Reusable Test Modules for Core Components:</strong> Developers can tap into a library of prebuilt test cases covering common UI elements, API responses, and database operations. For example, if a developer is working on an API endpoint requiring response verification, they can leverage our framework’s existing functions, saving time and maintaining consistency.</li><li><strong>Edge Case Scenarios: </strong>To ensure robust testing beyond the “happy path,” our framework includes sample tests for edge cases related to UI handling, complex API interactions, and challenging database queries. This foundation enables developers to build out comprehensive tests that catch potential pitfalls early.</li><li><strong>Expandable Architecture:</strong> A standout feature of our framework is its flexibility. Developers can seamlessly add modules or customize existing ones to fit specific project needs, accelerating development and reducing reliance on additional QA support.</li><li><strong>Advanced Configuration for Power Users:</strong> For those looking to push boundaries, our framework offers adjustable configurations, allowing developers to simulate unique user conditions and set custom preconditions for deeper test coverage.</li></ol><p><strong>Integrating Automation at Every Development Milestone</strong></p><p>A pivotal advantage of our framework is its ability to support immediate test creation upon completion of each feature or story. Rather than waiting for a comprehensive QA cycle, developers and QA engineers can ensure each new addition is validated instantly. This real-time approach ‘enhances test coverage from the start and lays the groundwork for robust regression testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*4c7FQTPQMXAXP7cv7TVb1A.png" /></figure><p><strong>Shifting Left: Early Bug Detection</strong></p><p>The “shift left” strategy has been a game changer for us. By embedding automated testing earlier in the development lifecycle, the QA team now has the potential to reduce the frequency and severity of bugs found in later stages through fast feedback in our pipelines. Historically, internal defects were uncovered during regression testing, our proactive approach has redefined our release process, enabled smoother, more predictable launches and reduced rework costs.</p><p><strong>Reducing Manual QA Dependence</strong></p><p>While developer-led testing hasn’t replaced the need for our skilled QA team, it has significantly changed their focus. QA engineers now have more bandwidth to concentrate on exploratory and integration testing, rather than being tied down by routine manual checks. This redistribution of responsibilities has led to more strategic, high-impact testing while maintaining a comprehensive safety net for core functionalities.</p><p><strong>Building Stakeholder Confidence in Releases</strong></p><p>Stakeholders now have the confidence to push changes knowing the code has passed rigorous, automated checks, including edge cases. This assurance is especially valuable for intricate, interlinked system components. The ability to independently validate their work has bolstered team confidence and has become a key factor in our reliable, high-quality releases.</p><p><strong>Conclusion</strong></p><p>Enable’s approach to developer led automation bridges the traditional gap between development and QA. By empowering developers to write custom, feature-specific tests during the development phase, we have increased test coverage, pre-empted bugs, and allowed our QA team to shift focus to higher value activities. This strategy has improved the quality of our release cycles, fostering a collaborative environment where quality ownership is shared across the team.</p><p>Our hope is that our continued investment into this shared automation framework which highlights Enable commitment to quality, improves our ability to release quality features to our customers and our team is committed to adapting our framework to the needs of our engineers as we endeavour on new projects and initiatives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f05dac632986" width="1" height="1" alt=""><hr><p><a href="https://blog.enable.engineering/automation-on-the-fly-writing-custom-tests-using-our-automation-framework-f05dac632986">Automation on the Fly: Writing Custom Tests Using Our Automation Framework</a> was originally published in <a href="https://blog.enable.engineering/">Enable Engineering Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>