<?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 Dilusha Rasangi Kumarage on Medium]]></title>
        <description><![CDATA[Stories by Dilusha Rasangi Kumarage on Medium]]></description>
        <link>https://medium.com/@dilushakumarage?source=rss-fe34b10a2a82------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*93QSz9WDu7-AGIRbDkASzQ.jpeg</url>
            <title>Stories by Dilusha Rasangi Kumarage on Medium</title>
            <link>https://medium.com/@dilushakumarage?source=rss-fe34b10a2a82------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:29:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dilushakumarage/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[Evolve or Fade : Thriving as a Software Tester in the Age of AI]]></title>
            <link>https://dilushakumarage.medium.com/evolve-or-fade-thriving-as-a-software-tester-in-the-age-of-ai-561ba05118c3?source=rss-fe34b10a2a82------2</link>
            <guid isPermaLink="false">https://medium.com/p/561ba05118c3</guid>
            <category><![CDATA[futureofsoftwaretesting]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[quality-engineering]]></category>
            <dc:creator><![CDATA[Dilusha Rasangi Kumarage]]></dc:creator>
            <pubDate>Sun, 15 Jun 2025 09:41:41 GMT</pubDate>
            <atom:updated>2025-06-16T11:45:05.249Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*ei-TC20RHIUJKbq1pzTHcA.png" /></figure><p>The software industry is undergoing a seismic shift. With the rapid rise of emerging technologies, the traditional role of the software tester is evolving at lightning speed. Testing is becoming more intelligent, predictive, and continuous.</p><blockquote><strong>Developers are shifting left — testers must shift smart</strong><br>Testers are no longer just bug hunters — they’re quality advocates, automation engineers, and AI collaborators.</blockquote><p>By embracing the emerging technologies and reshaping their skill sets, testers can not only stay relevant but also become <strong>indispensable</strong> in modern development teams.</p><blockquote>In this new reality, testers face a critical choice: <strong>evolve or fade</strong>.</blockquote><blockquote>But this isn’t a death sentence for QA —<strong> it’s a golden opportunity.</strong></blockquote><p>This blog explores, as a software tester, how you can thrive in the age of intelligent transformation via the following key points;</p><ol><li><a href="#5aa6">Understand AI &amp; Prompt Engineering Basics</a></li><li><a href="#0ad5">Use AI to Augment, Not Replace</a></li><li><a href="#3b67">Master Prompt Engineering for QA Tasks</a></li><li><a href="#f6e1">Learn Low-Code/No-Code Test Automation Tools</a></li><li><a href="#a03c">Strengthen Your Soft Skills</a></li><li><a href="#0cd2">Upskill Continuously</a></li></ol><h3><strong>1. Understand AI &amp; Prompt Engineering Basics</strong></h3><p><strong>AI (Artificial Intelligence)</strong> refers to systems that mimic human intelligence. In testing, it’s often used to generate test cases automatically, analyze logs and code, predict defects, suggest automation scripts, etc.</p><p>A big part of this shift is powered by <strong>Large Language Models (LLMs)</strong> like ChatGPT, Claude, and Gemini. These models can understand and generate human-like language based on the prompts you give them.</p><p><strong>Prompt engineering</strong> is the art of writing clear, effective instructions to get the best responses from AI tools.<br>The better your prompt, the more accurate and relevant the AI’s response will be.</p><p><strong>Example prompt to enter into AI-generated tools like ChatGPT, etc :</strong></p><p><strong><em>Task</em></strong><em>: Generate testcases<br></em><strong><em>Prompt</em></strong><em>: Act as a software tester. Generate 2 test cases for a user registration form with email and password</em></p><p>(You will learn about more prompts in the upcoming subtopic “Master Prompt Engineering for QA Tasks”)</p><h3>2. Use AI to Augment, Not Replace</h3><p>AI is a powerful assistant, not a replacement, for skilled software testers.</p><p><strong>How to use it effectively:</strong></p><ul><li>Let AI assist with “grunt work” — like test case generation, test data creation, summarizing bugs, exploratory testing or even generating automation code.</li><li>Don’t blindly trust results — your critical thinking, domain knowledge, and decision-making remain essential to validate AI-generated outputs.</li></ul><p>AI lacks full business context, critical thinking, and real user empathy. Your judgment is irreplaceable.</p><p><strong>Example :</strong></p><p><em>You ask ChatGPT: “Explain this stack trace in plain English.”<br> It gives you a clear breakdown, saving time — but you still verify its accuracy before reporting the root cause.</em></p><h3>3. Master Prompt Engineering for QA Tasks</h3><p>Prompt engineering isn’t just a buzzword — it’s a core skill for modern testers. Learn how to craft prompts that get exactly what you need from AI.</p><p><strong>Best Practices:</strong></p><ul><li>Use structured prompts.</li><li>Iterate and refine until the output is useful.</li><li>Learn limitations that LLMs have (e.g., hallucinations, lack of state awareness)</li><li>Save and reuse effective prompts as templates.</li></ul><p><strong>Example QA Prompts:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*m9ezjyrspePwFUEfc9wzpQ.png" /></figure><h3>4. Learn Low-Code/No-Code Test Automation Tools</h3><p>As a tester, you don’t need to be a full-time coder to contribute to automation. Thanks to <strong>low-code and no-code test automation tools</strong>, you can now build and maintain automated tests with minimal programming knowledge.</p><p>These tools democratize automation, enabling manual testers to contribute to continuous testing pipelines without deep coding backgrounds.</p><p>Thanks to the rise of <strong>AI-embedded low-code / no-code tools</strong>, testers can now automate intelligently without writing complex scripts.</p><p><strong>Examples of AI-embedded low-code and no-code test automation tools:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*IwQjwHRlt492Qtwyk3AG8g.png" /></figure><p><strong>AI coding assistants</strong> are transforming how testers and developers write code, including test scripts, automation frameworks, and debugging logic. This makes test automation faster and easier, so testers can cover more without extra work.</p><p><strong>Examples of Popular AI Coding Assistants:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*IF921SBJi0eyz_7Qpu13SQ.png" /></figure><h3>5. Strengthen Your Soft Skills</h3><p>As technical tasks become more automated, <strong>human-centric skills</strong> become your biggest differentiator.<br>A tester needs to communicate the limitations of an AI-driven test suite to a non-technical product owner. Clear, empathetic explanation builds trust and drives better decisions.</p><p><strong>Key soft skills for testers in the AI age:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*QjS3YIWZ9yrvG6hreUSZpg.png" /></figure><h3>6. Upskill Continuously</h3><p>The testers who thrive will be those who keep learning, not just tools, but principles of AI, ethics, and data.</p><blockquote>Upskilling isn’t a one-time activity — it’s a habit.</blockquote><p>A tester can spend a few hours per month on courses like “AI for Testers” or “Prompt Engineering with LLMs. This will build long-term career resilience.</p><p><strong><em>Examples:</em></strong></p><ul><li>Learn basic AI concepts (ML models, NLP, etc.)</li><li>Try tools like ChatGPT, LangChain, or even AutoGPT to experiment</li><li>Learn about AI Assistant tools to reduce the time spent on test automation</li><li>Take micro-courses or certifications on AI in testing (ISTQB is even updating their syllabi to reflect this shift).</li></ul><p><strong><em>Stats to note:</em></strong></p><ul><li><em>PwC (2024): 77% of workers are ready to learn new skills to stay competitive.</em></li><li><em>Coursera: Just 4–6 hours/month of upskilling led to measurable career growth for tech professionals.</em></li></ul><h3>Traditional QA vs. AI-Empowered QA</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*i-R_mwAD5zsYvmdoGvV4-A.png" /></figure><h3>Final Thoughts</h3><ul><li>The rise of AI and prompt engineering doesn’t mean the end of software testing — it signals a new beginning.</li><li>The testers who will lead the future aren’t the ones with the most certifications. They’re the ones who keep learning, experimenting, and adapting.</li><li>Testers who embrace these technologies, while doubling down on their uniquely human strengths, will not only survive but thrive.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*Fcx8VBvJkpIsfHJd8x4Vow.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=561ba05118c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Do the Majority of Test Automation Projects End in Failure?]]></title>
            <link>https://dilushakumarage.medium.com/why-do-the-majority-of-test-automation-projects-end-in-failure-bb0c2992477b?source=rss-fe34b10a2a82------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb0c2992477b</guid>
            <dc:creator><![CDATA[Dilusha Rasangi Kumarage]]></dc:creator>
            <pubDate>Thu, 20 Apr 2023 04:42:30 GMT</pubDate>
            <atom:updated>2023-04-20T04:42:30.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*F1QWQgETOXRbt1T2pUn5QQ.png" /><figcaption>Image source: <a href="https://www.perfecto.io/blog/types-of-test-cases-to-automate">https://www.perfecto.io/blog/types-of-test-cases-to-automate</a></figcaption></figure><p>“Automation”, When teams and companies hear the word “Test Automation,” they frequently become enthusiastic. It’s similar to a new device that, at first, everyone wants a piece of. Nevertheless, after a month or two, nobody is interested anymore, and we turn our attention to other project priorities and advancements.</p><p>Companies need to approach ‘Test Automation’ with realistic goals, the correct mindset, and a commitment to make it work for them if they want it to be a long-term success rather than just a passing fad.</p><p>Regardless of the domain or organization, there are a few common problems that plague new automation initiatives. Here, I’ll outline some of the key causes for automation efforts to fail, and keeping these pitfalls in mind will help you to avoid them and instead build stable and a reliable automation framework.</p><ol><li><a href="#17a4"><strong>Lack of Planning</strong></a></li><li><a href="#a309"><strong>Lack of Technically-Skilled Resources</strong></a></li><li><a href="#f392"><strong>Minimal Visibility around Automation</strong></a></li><li><a href="#e701"><strong>No Procedure to Handle Flaky Tests</strong></a></li><li><a href="#951a"><strong>The Goals of the Automation are Vague</strong></a></li><li><a href="#c754"><strong>Lack of Manual Testing Knowledge</strong></a></li><li><a href="#abb5"><strong>Lack of Maintenance</strong></a></li></ol><h3><strong>1. Lack of Planning</strong></h3><p>The lack of a strong plan for your test automation project causes needless delays, high-cost overruns, and insufficient test coverage. You must be certain of your test automation goals and the steps you will take to achieve them before you can move further.<br>This is the time to ask and answer every possible question about the project, such as;</p><ul><li>What technology stack/ tools would be appropriate and effective?</li><li>Which test cases are going to be automated? , which ones will still need a certain amount of human involvement?</li><li>Who will write the test scripts? , who will be responsible for maintaining them?</li></ul><p><strong><em>Solutions;</em></strong></p><ul><li>Choose the right tool mainly based on the technology stack of the system, scalability, compatibility, ease of writing test scripts and maintenance, reporting mechanism, cost, and risk coverage.</li><li>Refrain from attempting to automate every test case at once. A much better strategy that will result in a more effective deployment is to prioritize the most crucial test cases first, and then build on that process gradually.</li><li>Try to automate things that are reliable, less likely to change, need to be done repeatedly, or would help us save valuable testing time.</li></ul><h3>2. Lack of Technically-Skilled Resources</h3><p>Doing automation the right way requires testers to have a certain level of technical expertise. <br>Even though it might be costly and time-consuming to find qualified individuals with sufficient technical understanding, it is always wise to hire testers having deep technical knowledge. So that the returns you will be getting will be worth it.</p><p><strong><em>Solutions;</em></strong></p><ul><li>Hire at least a small number of technical testers who can launch automation projects and coach other team members to involve in the automation effort.</li><li>If there aren’t enough technical resources available or it’s not possible to recruit some technical testers, invest in a tool that anyone can use to perform automation, regardless of technical proficiency.</li></ul><h3>3. Minimal Visibility around Automation</h3><p>It’s often seen that out of all the team members, only a few members are in charge of automation and no one else has any clue of what is going on in terms of the automation efforts.<br>If you are unable to demonstrate how your efforts contribute to the solution of testing problems and add value, you are setting yourself up for failure. This is because no one will take your work seriously.</p><p><strong><em>Solutions;</em></strong></p><ul><li>Maintain documentation related to the automation such as ‘Tool Selection’, ‘Framework Setup’, ‘Automation Test Strategy’, Failure Analysis, Deviation plans, ROI of Test automation, etc.</li><li>Make your automation outcomes accessible to the entire team through email notifications and dashboards, and discuss the progress in daily stand-ups and other team meetings.</li><li>Share the ROI of the ‘Test Automation’ periodically with appropriate facts such as time-saving over manual intervention and a number of bugs that could be tracked and etc.</li></ul><h3>4. No Procedure to Handle Flaky Tests</h3><p>‘Flaky tests’ are one of the biggest hurdles in maintaining reliable automation frameworks.</p><p>We frequently hear testers reporting that tests are passing locally but failing on CI, or that some tests fail randomly. Simply a ‘Flaky test’ is a test that is considered to be flaky when it can pass and fail across multiple retry attempts without any code changes.</p><p>Teams lose interest in automation as a result of these claims, and testers begin to doubt their own tests.<br>So, it’s critical to identify the underlying reason for such failing tests (Flaky tests).</p><p><strong><em>Solutions;</em></strong></p><ul><li>Do not get overwhelmed by flaky tests. Even though finding the source of these sporadic failing tests can be frustrating, take it as a way to improve in thinking strategy and try to find solutions by yourself or pair up with another tester or developer.</li><li>Try to put the failing tests in groups and identify a unifying pattern. There might be a common theme between failing tests.</li><li>A test may pass when it’s run individually but fails while running in combination with other tests. If it’s that the case, check the test/tests which ran previously and run both together.</li><li>Most of the ‘Test automation’ tools contain inbuild functions to detect, flag, and track flaky tests. Try to use them.<br><strong>Ex</strong>: <a href="https://docs.cypress.io/guides/cloud/flaky-test-management">https://docs.cypress.io/guides/cloud/flaky-test-management</a></li><li>Apply ‘Auto Retry’ for E2E UI Test Automation Suits to reduce the Test Flakiness.<strong><br> Ex: </strong><a href="https://docs.cypress.io/guides/guides/test-retries">https://docs.cypress.io/guides/guides/test-retries</a></li></ul><h3>5. The Goals of Automation are Vague</h3><p>We begin with creating a robust automation framework with wonderful goals like running in a stable and consistent manner, being maintainable, seamlessly integrating with the CI/CD pipeline, etc.</p><p>All these goals are perfect on paper. However, when it comes to executing the steps, there is a severe lack of clarity among team members.</p><p>This is one of the main reasons for the failure of automation projects where the team begins with doing something complex with automation, but when they discover they are not reaping the expected benefits, they are forced to refactor the entire system.<br>As a result, the team ends up losing a lot of time, money, and effort.</p><p><strong><em>Solutions;</em></strong></p><ul><li>Pick out a few stable functionalities in the system and begin with their automation initially. Next, you can gather feedback on what went well, what went wrong, and suggestions to improve the framework and the scripts. Once you achieve consistency in test runs, you can gradually start automating the other functionalities.</li><li>Needs may vary for different project contexts, therefore apply a customized approach for executing the test automation projects. <br>Creating separate automation projects as a personal preference will be a fantastic idea; Ex :<br> - <strong><em>Smoke Test Suite: </em></strong>Runs automatically after every code check-in<br> - <strong><em>Regression Test Suite: </em></strong>Runs on a daily basis as scheduled</li></ul><h3>6. Lack of Manual Testing Skills</h3><p>The tester should have solid knowledge and expertise in functional testing carried out manually in order to flourish as an automation tester. It will be beneficial if the tester has a strong understanding of the domain in addition to application knowledge and scripting skills.</p><p>The automation test team cannot accomplish adequate test coverage and greater test accuracy if they are not well-versed in the application’s functionality, the domain, and end-user thinking.<br>If the automated scripts don’t cover the right test scenarios and the scope, this will cause the Test Automation projects to fail.</p><p><strong><em>Solutions;</em></strong></p><ul><li>Automation testers must have a thorough understanding of the STLC (Software test life cycle) and how the testing is performed at each step just as manual testers do.</li><li>If the Automation testers have thorough functional knowledge of the application and are well-versed in the domain, they can increase test accuracy and coverage in test automation.</li></ul><h3>7. Lack of Maintenance</h3><p>Implementing automated tests is an investment. It almost always costs more than manual testing. The cost of doing tests is significantly decreased by automation because human intervention is no longer necessary.</p><p>The maintenance of manual tests is not very costly in terms of time, However, this is not the case with automated tests. Since automated tests typically consist of code, their upkeep is more expensive than manual testing’ because the tests must be modified or regenerated.</p><p>Automated test maintenance is crucial because if they are not up to date, they will not be able to achieve their goal. Unmaintained tests add up, creating a technical debt that keeps rising.<br>If the automated tests continue to fail but are disregarded by the team because they are not up to date, this will result in coverage gaps that cause significant or catastrophic production failures that these tests would have caught. Then the test automation project will become obsolete and be abandoned.</p><p><strong><em>Solutions;</em></strong></p><ul><li>In order to avoid the problem of maintenance, you must obviously maintain your tests. But as this may time consuming and costly, the team must put in place certain good practices to avoid this problem as follows;<br>- <strong><em>Limit the number of tests</em>: </strong>So that the maintenance is sustainable by the team<strong><br>- <em>Build your tests in order to limit their maintenance: </em></strong>Automated tests are code. As such, good code practices must be used.</li></ul><h3>Conclusion</h3><ul><li>Keep an eye on the aforementioned criteria to avoid having test automation initiatives fail.</li><li>Take the essential actions to avoid failure with test automation projects.</li><li>Keep up the enthusiasm we had when we first began the test automation.</li><li>Foster an automation testing culture in your organization for successful test automation projects.</li><li>Consider yourself to be a full-stack quality engineer.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb0c2992477b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emerging Trends & Technologies in Software Testing]]></title>
            <link>https://engineering.99x.io/emerging-trends-technologies-in-software-testing-9adce39c328?source=rss-fe34b10a2a82------2</link>
            <guid isPermaLink="false">https://medium.com/p/9adce39c328</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[quality-engineering]]></category>
            <category><![CDATA[emerging-technology]]></category>
            <category><![CDATA[emerging-trends]]></category>
            <dc:creator><![CDATA[Dilusha Rasangi Kumarage]]></dc:creator>
            <pubDate>Mon, 07 Mar 2022 16:40:37 GMT</pubDate>
            <atom:updated>2022-10-28T07:39:00.240Z</atom:updated>
            <content:encoded><![CDATA[<p>In recent years, there has been a great evolution in the field of the ICT industry. Hence, software testing which is an integral part of it also has been evolved with new trends of testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDJMSOjVF4nachs2jRSTaw.jpeg" /></figure><p>Commonly ICT professionals are familiar with the below trends of software testing. Most of these techniques and strategies came into play a few years back.</p><ul><li><strong>Test Pyramid Approach</strong> which is a prevention-focused methodology. It promotes testers to prevent bugs as opposed to explicitly testing for bugs.</li><li><strong>Transfer from Quality Assurance to Quality Engineering </strong>where the tester can assess technical risks even before an app’s development begins.</li><li><strong>Be a Full-stack Quality Engineer </strong>who can test the system in both domain &amp; quality aspects using manual techniques &amp; test automation techniques as well.</li></ul><p>With an eye towards staying at the top of the industry &amp; being competitive, delivering an excellent customer experience is a must. These include deploying superior quality software capable of performing well &amp; the ability to implement quick updates of software based on market demand.</p><blockquote><strong>This is where proper software testing comes into play.</strong></blockquote><p>With the newly evolved technologies in software development, Tester&#39;s face challenges such as;</p><ul><li>Testing the software on multiple devices having different UI &amp; hardware configurations</li><li>Adherence to the growing industry</li><li>Testing software&#39;s which performs frequent updates</li><li>Up to date with technology amendments &amp; select tools of testing wisely</li><li>Ensure faster release cycles</li></ul><p>To overcome these challenges, organizations need to reconsider their test methodologies and strategies.</p><blockquote><strong>This is where new technologies of software testing come to play &amp; these emerging technologies can reshape the future of software testing.</strong></blockquote><h3>Let’s look into the overview of the below-emerging trends &amp; technologies in software testing.</h3><ol><li><a href="#4d9a"><strong>Artificial Intelligence (AI) and Machine Learning (ML)</strong></a></li><li><a href="#4cf0"><strong>Big Data Testing</strong></a></li><li><a href="#2eaa"><strong>Robotic Process Automation (RPA)</strong></a></li><li><a href="#1513"><strong>QAOps or DevTestOps</strong></a></li><li><a href="#e8ca"><strong>Internet of Thing (IoT)</strong></a></li></ol><h3><strong>Artificial Intelligence (AI) and Machine Learning (ML)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o10KThjEMVqdpXWu.jpg" /><figcaption>Image source : <a href="https://etfdb.com/themes/artificial-intelligence-etfs/">https://etfdb.com/themes/artificial-intelligence-etfs/</a></figcaption></figure><p><strong>Artificial intelligence</strong> describes the concept of machines being able to be intelligent and complete “smart” tasks that were originally thought to require human intelligence.</p><p><strong>Machine learning </strong>is a form or subset of artificial intelligence where machines are given data and then allowed to make sense of it. Over time, algorithms improve through an experience similar to human development (learning patterns) &amp; take decisions with minimal or no human intervention.</p><p>As the first step, we must identify the areas within the testing process that can be optimized with <strong>AI</strong>(Artificial Intelligence) and apply the <strong>ML</strong>(Machine Learning) and <strong>DL</strong>(Deep Learning) algorithms.</p><p>AI and ML plays a vital role in driving quality engineering related to the following aspects;</p><ul><li><strong>Do some predictive analysis on customers’ data</strong> to generate target reports/outcomes</li><li><strong>Optimize the testing process</strong> by gaining data-driven insights via AI &amp; MI tools. i.e. Analyze the test results to predict vulnerabilities, optimize code, and report defects</li><li><strong>Visual validation &amp; Spidering </strong>i.e. ML-based visual validation tools which can create a simple machine learning test that automatically detects all the visual &amp; performance-related bugs in the software according to the pattern analysis</li><li><strong>Test Automation (Unit/API/UI)</strong> i.e. Generate &amp; execute tests over more expansive areas. ML learns patterns and uses the data to improve the reliability of the tests.</li></ul><h4><strong>AI-based testing tools</strong> that are quite popular in the market are as follows;</h4><ol><li><a href="https://www.test.ai/">Test.AI</a></li><li><a href="https://applitools.com/">Applitools</a></li><li><a href="https://www.mabl.com/">Mabl</a></li><li><a href="https://www.perfecto.io/products/testcraft">TestCraft</a></li><li><a href="https://saucelabs.com/">Sauce Labs</a></li><li><a href="https://retest.de/">Retest</a></li></ol><p>Smart algorithms can optimize the testing process &amp; support testers to find the maximum number of bugs in less time. It will make the application more reliable &amp; accurate.</p><blockquote><strong>The outcomes of AI &amp; ML testing of testers can be used to refine the product by developers &amp; it will result in making a smarter and more productive software for the end-user.</strong></blockquote><h3><strong>Big Data Testing</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d80JPIRdjRSYxwGJ.png" /><figcaption>Image source: <a href="https://www.msystechnologies.com/blog/8-steps-to-foolproof-your-big-data-testing-cycle/">https://www.msystechnologies.com/blog/8-steps-to-foolproof-your-big-data-testing-cycle/</a></figcaption></figure><p>Simply big data means a large volume of data.</p><blockquote><strong>Gartner defines Big Data as</strong>, “Big data is high-volume, high-velocity and/or high-variety information assets that demand cost-effective, innovative forms of information processing that enable enhanced insight, decision making, and process automation”.</blockquote><p>Therefore to be accurate in the business decisions and other activities, it is essential for any software company to strengthen big data testing and deliver valuable insights about various products and services.</p><blockquote>According to <strong>Evans Data Corporation</strong>, “<strong>19.2% of big data app developers say quality of data is the biggest problem they consistently face</strong>”.</blockquote><p>There are several types of testing available for testing each characteristic of big data. At a glance, you can get a big picture of it via the below diagram</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5EqmrdZi6xtVKrGr-UB8_Q.png" /></figure><h4>Let’s discuss some of the challenges in Big Data Testing</h4><ul><li><strong>Data Harnessing (Cleansing)</strong><br><strong><em>Challenge</em></strong>: Dealing with both structured and unstructured data which makes sampling strategy very difficult.<br><strong><em>Solution</em>:</strong> Perform in-depth analysis of structured and unstructured data to convert them into a valuable format.</li><li><strong>Data Quality &amp; Completeness</strong><br><strong><em>Challenge</em></strong>: It is difficult to make sure that complete data is pulled into the system pulled from various sources like RDBMS, weblogs, social media, etc<br><strong><em>Solution</em>: </strong>Use tools like Presto, Talend and Datameer to verify the completeness of the data in HDFS.</li><li><strong>Displaying Meaningful Results</strong><br><strong><em>Challenge</em></strong>: Creating the BI reports from Big Data becomes difficult when dealing with extremely large amounts and diverse data.<br><strong><em>Solution</em>: </strong>One way to resolve this is to cluster data into a higher-level view where smaller groups of data become visible.</li><li><strong>Test Environment Setup</strong><br><strong><em>Challenge</em></strong>: Creating an effective test environment, multiple testing nodes for Big Data testing.<br><strong><em>Solution</em>: </strong>Take care of the environment to handle the Big Data effectively and efficiently.</li><li><strong>Performance Testing</strong><br><strong><em>Challenge</em></strong>:Faster data processing, work load, and network load balancing to ensure real time data synchronization.<br><strong><em>Solution</em>:</strong>Have good infrastructure to store and process large amount of data in given time intervals to meet the performance.</li></ul><h4>Big Data Testing Tools that are quite popular in the market are as follows;</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*s3ZO2-Rkb6LS8zFhHA23mQ.png" /></figure><blockquote><strong>Insights of big data testing can be used to improve the quality of products and services, hence the organizations can deliver a better customer experience.</strong></blockquote><h3>Robotic Process Automation (RPA)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vtTA5rPLgb37PFmC.jpeg" /><figcaption>Image source: <a href="https://www.imt-soft.com/Blogs/All/Robotic-Process-Automation---RPA-what-is-it-">https://www.imt-soft.com/Blogs/All/Robotic-Process-Automation---RPA-what-is-it-</a></figcaption></figure><p><strong>RPA</strong> is the technology that creates a virtual workforce (or we can call software bots) to imitate human actions and automate repetitive and rule-based processes.</p><p>Customers demand faster &amp; better output, hence organizations tend to implement RPA to automate the processes to optimize them with minimum errors.</p><blockquote>Throughout the software testing activities, we can use RPA to optimize the repetitive testing activities to automate large and complex data sets through an easy-to-use interface. <strong>RPA has the capability to perform all types of testing that use automation testing tools, thereby eliminating the need to write test scripts.</strong></blockquote><h4>Demanding features of RPA in Test Automation</h4><ul><li><strong>Code-less</strong>: No programming skills required</li><li><strong>Adaptable</strong>: Possible to schedule monitoring of work and can operate 24*7</li><li><strong>Cost Saving</strong>: Huge cost reduction as a very minimal workforce is required</li><li><strong>Accuracy</strong>: Bots governed by algorithms accurately perform actions</li><li><strong>Flexibility</strong>: Platform independent. Supports a web-based, legacy, desktop, or mobile application</li><li><strong>Scalability</strong>: Virtual workforce can be assigned anytime, and allows parallel execution</li><li><strong>Data Migration and Change Management:</strong> Robots that work on legacy systems can easily be used to preserve the application’s data and integrity and they can also re-use the existing application logic, databases, and validation without high re-structuring or maintenance costs.</li><li><strong>Cognitive Automation:</strong> RPA integrates structured and unstructured data using different AI features and extends the automation to more processes using cognitive capabilities for predictive analysis.</li></ul><h4>Let’s have a look at the<strong> differences between Test Automation &amp; Robotic Process Automation</strong>.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQgPLLy8rsrhBddJ9dJqdA.png" /></figure><h4>Due to the outstanding features of RPA, organizations return the following benefits;</h4><ul><li><strong>Cost Reduction: </strong>Bots are cost-effective since they save time and generate output with precision</li><li><strong>Reduce errors &amp; Enhance accuracy: </strong>RPA reduces the rate of human errors as mundane manual tasks are automated</li><li><strong>Increased throughput and output:</strong> RPA testing supports the throughput of Big Data Testing that enhances the overall quality and maintenance of your end product even after it hits the market.</li></ul><h4><strong>RPA tools</strong> that are quite popular in the market are as follows;</h4><ol><li><a href="https://www.blueprism.com/">Blue Prism</a></li><li><a href="https://www.uipath.com/">UiPath</a></li><li><a href="https://www.automationanywhere.com/">AutomationAnywhere</a></li><li><a href="https://www.pega.com/">Pega</a></li><li><a href="https://www.sap.com/products/robotic-process-automation.html">Contextor</a> (now part of SAP):</li><li><a href="http://guru99.link/recommends-zaptest-rpa">ZAPTEST</a></li><li><a href="https://bit.ly/2mwX82y">HelpSystems</a></li><li><a href="https://bit.ly/3glse6g">JAMS</a></li><li><a href="https://fxo.co/CIfb?fobs=robotics-process-automation-tools">Kofax</a></li><li><a href="https://guru99.live/gemQ7A">Power Automate</a></li></ol><blockquote><strong>RPA enables work to go on 24/7 without any break and with precision. This, in return, guarantees a superior customer experience.</strong></blockquote><h3><strong>QAOps or DevTestOps</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*eDRo0L9lihqCdpkTrLnqnw.png" /><figcaption>Image source: <a href="https://www.softwaretestingmaterial.com/qaops/">https://www.softwaretestingmaterial.com/qaops/</a></figcaption></figure><p><strong>DevOps</strong> as a term originated in 2009 following a talk at the O’Reilly Velocity Conference titled “10+ Deploys per Day: Dev and Ops Cooperation at Flickr.”</p><p><strong>DevOps</strong> is a set of practices that combines software development and IT operations intending to provide fast and continuous delivery by adhering to the DevOps key principles.<br><strong>QA</strong> is playing a crucial part in the complete software development intending to deliver a better quality product.</p><blockquote>And the combination of these two methodologies, i.e. <strong>QA and DevOps</strong> brings a new practice called <strong>QAOps</strong> or <strong>DevTestOps</strong>.</blockquote><p><strong>QAOps</strong> is the practice of integrating quality assurance (QA) into the CI/CD pipeline. This means that the software testing process should be integrated into the CI/CD pipeline rather than being an isolated process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*_hmd_iQU7PmFrLvX3zUvdg.png" /></figure><p>There are several ways to approach the implementation of QAOps.</p><ol><li><strong>Smoke Testing</strong>: Smoke Testing is used to check the stability of the product. QAOps leverages smoke testing for verification testing.</li><li><strong>Automated Testing: </strong>Automated Testing enables to testing of the software at a faster pace. This is leveraged by the QAOps framework by executing the automated codes as a part of the QAOps pipeline.</li><li><strong>Regression Testing: </strong>Regression Testing allows checking the reliability of the product when it is updated with a new feature or an existing feature is enhanced. QAOps checks if the quality of the software is maintained with the introduction of the new features or modifying the code.</li><li><strong>Parallel Testing</strong>: Parallel Testing allows running multiple test cases on an application and its subcomponents across operating systems and browsers for a product simultaneously which reduces the overall testing time. QAOps uses CI/CD pipeline for parallel testing which instantly enables faster testing.</li><li><strong>Scalability Testing:</strong> Scalability Testing depicts how the software will behave when the usage will increase or decrease in the longer run. The tests should be able to synchronize with the data and the process during scale up or down and we can achieve it via QAOps by leveraging scalability testing in the pipeline.</li></ol><blockquote><strong>QAOps is a useful set of practices/framework that automates the processes among software development, operations and QA to deliver a software faster and more reliably by identifying bugs at an earlier stages.</strong></blockquote><h3><strong>Internet of Thing (IoT)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2CT29vqA4j233yx2.jpeg" /><figcaption>Source: <a href="https://performancelabus.com/iot-testing-importance/">https://performancelabus.com/iot-testing-importance/</a></figcaption></figure><p>The term “<a href="https://www.simplilearn.com/what-is-iot-how-and-why-it-matters-article">Internet of Things</a>” or IoT was first coined by Kevin Ashton in 1999. But it was only when Gartner added IoT to its list of new emerging technologies in 2011</p><p><strong>The Internet of Things (IoT)</strong> deals with millions of devices by providing easy controls and remote access to information and services via a smartphone, smartwatch, or tablet from anywhere in the world.</p><p>It connects different objects that are provided with unique identifiers and the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.</p><blockquote>Any physical object can be transformed into an IoT device if it can be connected to the internet to be controlled or communicate information.</blockquote><h4><strong>The main types of IoT devices </strong>are as follows;</h4><ol><li><strong>Consumer IoT</strong>: Primarily for everyday use. <br>Eg: home appliances, voice assistance, and light fixtures.</li><li><strong>Commercial IoT</strong>: Primarily used in the healthcare and transport industries. <br>Eg: smart pacemakers and monitoring systems.</li><li><strong>Military Things (IoMT)</strong>: Primarily used for the application of IoT technologies in the military field. <br>Eg: surveillance robots and human-wearable biometrics for combat.</li><li><strong>Industrial Internet of Things (IIoT)</strong>: Primarily used with industrial applications, such as in the manufacturing and energy sectors. <br>Eg: Digital control systems, smart agriculture, and industrial big data.</li><li><strong>Infrastructure IoT</strong>: Primarily used for connectivity in smart cities. <br>Eg: infrastructure sensors and management systems.</li></ol><p>Nowadays, different sets of products enter the IoT market. IoT testing involves real-time intelligence and communication to ensure perfect harmony between hardware and software throughout the connected network. Due to this, IoT testing is undergoing changes in terms of approaches and scenarios.</p><blockquote><strong>A typical IoT platform has four basic components: application, sensors, backend database (data center), and network communication.</strong><br>Each component of the IoT needs different testing procedures. Testers need to consider these elements to formulate a comprehensive test strategy.</blockquote><h4>Let’s discuss some of the <strong>popular trends and scenarios of IoT testing</strong>:</h4><ol><li><strong>Artificial Intelligence (AI): </strong>The effect of AI in IoT testing can reduce extensive human hours and inaccuracies/discrepancies which results in ensuring a more reliable product. Testers can consider it to drive automation, expand coverage and enhance efficiency in all the areas of IoT testing.</li><li><strong>IoT Network Security Challenges: </strong>Securing the data and its privacy is very critical and authorizations play a very important role in IoT data streaming and transfer. <br>It might be difficult to secure all the connected devices since the components or modules of IoT are not as simple as that of PCs and smartphones. Considering these security challenges in IoT, QA professionals must assess a full range of potential vulnerabilities in IoT products and services.</li><li><strong>Big Data Testing: </strong>The volume, value, variety, and variability of data generated by IoT systems and devices can be a huge challenge in IoT testing soon. Each type of data set requires different types of testing techniques and testers will have to adapt their testing skills accordingly.</li><li><strong>Micro Services Test Automation: </strong>Microservice architecture involves developing a single application that can work together as a suite of small services. When it comes to IoT, each of these services can run as an individual process and communicate with lightweight mechanisms such as an HTTP resource API.<br>Utilizing Microservices for IoT testing will also offer the benefits of testing the extensibility, scalability, and integrations of the IoT system. <br>Microservices test automation in IoT will reduce the complexity of testing a huge architecture as each microservice can be tested as a separate process.</li><li><strong>Testing For a Wide Range of Interfaces: </strong>Depending upon the type and number of connected IoT devices, it is necessary to test the integrations and interfaces to ensure appropriate coverage and universal functionality across all the touchpoints.<br>If we consider the video streaming sites such as Netflix and Amazon Prime can be accessed on a variety of devices from HDTVs, smartphones to a gaming console. <br>Therefore it is important to test the video streaming functionalities on all the platforms and connected devices are required to test on acceleration, vibration, stability, repetition, stress, memory, or endurance factors.</li><li><strong>Testing Wireless Connectivity Scenarios: </strong>Connectivity throughout the IoT network is dependent on many wireless standards like Wi-Fi, ZigBee, 4G LTE, etc. This will result in different wireless testing scenarios.<br>Sometimes IoT devices could be out of range and so they will have to monitor the condition continuously. Therefore testing of various wireless scenarios will be an essential area to focus on IoT testing.</li></ol><h4>Top 5 Most Popular IoT Devices</h4><ol><li><a href="https://www.flipkart.com/google-home-assistant-smart-speaker/p/itm3918ee0aca603">Google Home Voice Controller</a></li><li><a href="https://www.amazon.in/Echo-Plus-2nd-Gen/dp/B07CTTL5GR">Amazon Echo Plus Voice Controller</a></li><li><a href="https://august.com/">August Doorbell Cam</a></li><li><a href="https://august.com/">August Smart Lock</a></li><li><a href="https://foobot.io/">Foobot</a></li></ol><blockquote><strong>As of 2021, there are 21.7 billion active connected devices in the world today, out of which more than 11.7 billion (54 percent) are IoT devices. This means that there are more IoT devices in the world than there are non-IoT devices.</strong></blockquote><h3>Conclusion</h3><ul><li>Lots of new trends &amp; technologies including above what I have discussed have already come to the party of the IT industry and are evolving day-by- day by reshaping with lots of new trends.</li><li>Organizations use these technologies to provide fast and reliable products to customers.</li><li>Software testers play an integral part in delivering a better quality software product to the customers, thus they should always be up to date with these new trends and technologies.</li><li>Learning &amp; being armful with trends would critically affect the software testers and will help yourself ready for the game.</li><li>As we all know, change is the law of life and it is going nowhere. So it is crucial to stay ahead of it. If you don’t want to get left behind, it’s essential to embrace these new trends &amp; technologies.</li></ul><h3><strong>References</strong></h3><ul><li><a href="https://bernardmarr.com/are-machine-learning-and-ai-the-same/">Are Machine Learning And AI The Same?</a></li><li><a href="https://u-tor.com/topic/ai-and-ml-in-software-testing">AI and ML in Testing: How to Make Your Test Automation more Intelligent - UTOR</a></li><li><a href="https://www.cigniti.com/blog/big-data-testing-digital-customer-experience/?utm_source=article&amp;utm_medium=hyperlink&amp;utm_campaign=DataVersity">The need of big data testing for digital customer experience</a></li><li><a href="https://www.testing-whiz.com/blog/how-robotic-process-automation-transforms-the-software-testing-industry">How Robotic Process Automation Transforms the Software Testing Industry</a></li><li><a href="https://www.softwaretestingmaterial.com/qaops/">QAOps - What it is? Process, Implementation &amp; Benefits</a></li><li><a href="https://www.einfochips.com/blog/top-6-popular-trends-and-scenarios-to-consider-in-iot-testing/">Top 6 Popular Trends and Scenarios to Consider in IoT Testing</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9adce39c328" width="1" height="1" alt=""><hr><p><a href="https://engineering.99x.io/emerging-trends-technologies-in-software-testing-9adce39c328">Emerging Trends &amp; Technologies in Software Testing</a> was originally published in <a href="https://engineering.99x.io/">Engineering at 99x</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cypress : Configure the Framework to Execute Scripts on Multiple Environments]]></title>
            <link>https://engineering.99x.io/cypress-configure-the-framework-to-execute-scripts-on-multiple-environments-e3c7aad11249?source=rss-fe34b10a2a82------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3c7aad11249</guid>
            <category><![CDATA[test-automation-framework]]></category>
            <category><![CDATA[cypress-automation]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[Dilusha Rasangi Kumarage]]></dc:creator>
            <pubDate>Fri, 28 Jan 2022 09:39:56 GMT</pubDate>
            <atom:updated>2022-10-28T07:12:08.622Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Configure Cypress Test Automation Framework to Execute Scripts in Multiple Environments?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mVHwWUZu0ptpWyrCdvCgYg.jpeg" /></figure><p>Multiple execution environments <strong>ensure that our application is rigorously tested before it is deployed and made available to end users.</strong></p><p>We use environments to create “stages” of the application that we consider good for releasing.<br>Each environment has its own unique purpose. There are different standards of environments that are used in the industry where almost every process starts at the ‘development’ stage and ends with ‘production’.<br>For example, the most commonly used environments are Development, QA, Staging &amp; Production.</p><p>Therefore, in order to assure that the application works fine in each environment, we have to consider the execution of our test automation suite also in some of these multiple environments. <br>When it comes to testing, we better execute our automation code at least in QA and Staging environments plus only applicable scenarios in a Production environment as well.</p><blockquote>Let’s discuss how could we achieve this in “<strong>Cypress Test Automation Framework</strong>”.</blockquote><p>Even though there are different ways to achieve this, I’m going to explain here is the method which I used in my test automation framework.</p><h3>Step 1: Create a file as ‘utility.js’</h3><ul><li>Navigate to the <strong>cypress/support</strong> folder in your Project<br>[<strong>Project Folder</strong> Root &gt; <strong>cypress </strong>folder &gt; <strong>support </strong>folder]</li><li>Create a Typescript file as <strong>utility.js </strong>inside the <strong>‘Support’ </strong>folder</li><li>Below is an example of the <strong>utility.js</strong> file</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*oY-0jc703jodnd_0hT_uUA.png" /></figure><h3>Step 2: Add code to ‘utility.js’ file to return the URL based on the Cypress environment variables</h3><p>Here we need to return the specific environment URL based on the value of the environment variable. <br>Cypress environment variable value will be passed from the command line / package.json file(will be explained in the later steps).</p><pre><strong>//utility.js</strong><br><br>export class Utility {<br>    getBaseUrl() {<br>        let envi = Cypress.env(&#39;ENV&#39;); <strong>//Get the value of environment variable i.e ENV</strong><br>        if (envi == &#39;production&#39;) //Check the value<br>            return &quot;<a href="https://www.proudction-website.com/">https://www.proudction-website.com</a>&quot;; <strong>//return desired url</strong><br>        else if (envi == &#39;staging&#39;)<br>            return &quot;<a href="https://www.staging-website.com/">https://www.staging-website.com</a>&quot;;<br>        else if (envi == &#39;qa&#39;)<br>            return &quot;<a href="https://www.qa-website.com/">https://www.qa-website.com</a>&quot;;<br>    }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r4qULES3Zmc3XJ5wDMfoLw.png" /></figure><p><strong>If we analyze the above example,</strong></p><ul><li><strong>getBaseUrl() Function</strong> : This will return a single URL based on the environment variable value<strong> </strong>we pass in the package.json file</li><li><strong>ENV</strong>: ENV is an environment variable that will be passed from the package.json file</li><li><strong>let envi = Cypress.env(&#39;ENV&#39;)</strong>: This will save the value of the Cypress environment variable to a local variable called envi</li><li><strong>if-else conditions : </strong>This will check the value of the environment variable i.e value of ENV in the package.json file</li><li><strong>if (envi == &#39;production&#39;):</strong>If the ENV=production in package.json file, system will return the production environment URL. Likewise for staging &amp; QA environments.</li></ul><h3>Step 3: Create a spec file and call the base URL</h3><p>Now we are ready with our own utility function which will return the environment-specific URLs. <br>Next , let’s create a Cypress spec file to call the base URL by importing the utility.js file.</p><pre><strong>//test1.spec.js</strong><br><br><strong>//Import Utility from support folder</strong><br>import { Utility } from &quot;../../../support/utility&quot;<br><br><strong>//Call getBaseUrl() to get environment specific url value</strong><br>const url = new Utility().getBaseUrl();<br><br>describe(&#39;Verify successful login to ABC Portal&#39;, function() {<br>    it(&#39;User should enter correct credentials&#39;, () =&gt; {<br>        cy.visit(url); <strong>//use url variable</strong><br>    });<br>});</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GhfZKUItQoAXFysyBjGAOg.png" /></figure><h3>Step 4: Configure package.json file with environment variables</h3><p>According to the example spec file given, the path to that spec is ‘cypress/integration/Smoke_Suit’.</p><p>Therefore we can configure the ‘package.json’ file to execute the test specs under ‘Smoke_Suit’ in chrome browser &amp; multiple environments as follows;</p><pre>//package.json</pre><pre>&quot;qa:smoke:scripts&quot;: &quot;cypress run --spec cypress/integration/Smoke_Suit/*.js --env ENV=qa --browser chrome&quot;,</pre><pre>&quot;stage:smoke:scripts&quot;: &quot;cypress run --spec cypress/integration/Smoke_Suit/*.js --env ENV=staging --browser chrome&quot;,</pre><pre>&quot;prod:smoke:scripts&quot;: &quot;cypress run --spec cypress/integration/Smoke_Suit/*.js --env ENV=production --browser chrome&quot;,</pre><pre>&quot;qa:smoke:test&quot;: &quot;npm run qa:smoke:scripts &quot;,</pre><pre>&quot;stage:smoke:test&quot;: &quot;npm run stage:smoke:scripts &quot;,</pre><pre>&quot;prod:smoke:test&quot;: &quot;npm run prod:smoke:scripts &quot;,</pre><h3>Step 5: Execute the Test Suite in multiple environments as specified</h3><p>Open a new terminal &amp; execute the suites in the wanted environment as follows;</p><p><strong>To Execute in QA Environment</strong></p><pre>npm run qa:smoke:test</pre><p><strong>To Execute in Staging Environment</strong></p><pre>npm run stage:smoke:test</pre><p><strong>To Execute in Production Environment</strong></p><pre>npm run prod:smoke:test</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3c7aad11249" width="1" height="1" alt=""><hr><p><a href="https://engineering.99x.io/cypress-configure-the-framework-to-execute-scripts-on-multiple-environments-e3c7aad11249">Cypress : Configure the Framework to Execute Scripts on Multiple Environments</a> was originally published in <a href="https://engineering.99x.io/">Engineering at 99x</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Locust : An Open-source Performance Testing Tool]]></title>
            <link>https://dilushakumarage.medium.com/introduction-to-locust-an-open-source-performance-testing-tool-6fc4054cce02?source=rss-fe34b10a2a82------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fc4054cce02</guid>
            <category><![CDATA[performance-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[locust]]></category>
            <category><![CDATA[test-engineering]]></category>
            <category><![CDATA[load-testing]]></category>
            <dc:creator><![CDATA[Dilusha Rasangi Kumarage]]></dc:creator>
            <pubDate>Thu, 27 May 2021 16:12:13 GMT</pubDate>
            <atom:updated>2021-05-28T13:37:21.553Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction to Locust : An Open-source Performance Testing Tool</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*S9qnZDsg9fxy3kBAeB1zfA.png" /><figcaption>Image source : <a href="https://coursemarks.com/course/performance-testing-using-locust-1-0/">https://coursemarks.com/course/performance-testing-using-locust-1-0/</a></figcaption></figure><p>Open-source Performance Testing Tools are not a new thing for us who are in Quality Engineering track. <br>We have a privilege to choose any of the tools according our preferences and the scope. Among them,</p><p><strong>Locust</strong> is a modern Load testing tool which allows us to specify loading scenarios by a Python code.</p><p>Let’s go through the following to get a basic idea of Locust Performance Tool.</p><ul><li><a href="#61e7">High-level picture of Performance Testing Vs Load Testing Vs Stress Testing</a></li><li><a href="#11b7">An overview of Locust</a></li><li><a href="#6116">Pros and Cons of Locust</a></li><li><a href="#5d98">Locust Vs JMeter</a></li><li><a href="#f0b5">Set up Locust on Windows</a></li><li><a href="#968c">First code with Locust</a></li><li><a href="#e32f">Running Locust via Web UI</a></li><li><a href="#80af">Running Locust via Command Line Interface</a></li><li><a href="#036b">Conclusion</a></li></ul><h3>High-level picture of Performance Testing Vs Load Testing Vs Stress Testing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*tGY8tEsJcL9sGOT2h6yS-g.png" /></figure><h3>An overview of Locust</h3><p>Locust is an easy to use, scriptable and scalable performance testing tool.</p><blockquote>According to the Locust website, <strong>it gets its name from the insect because of its swarming behavior mimicked by the tool</strong>. Some of the terminology used by Locust, like attacking, hatching, and swarming, are all inspired and borrowed from nature.</blockquote><ul><li>Each simulated user is like a locust and applies significant pressure on websites and applications.</li><li>This behavior is then monitored in real time on a web-based UI.</li><li>Each Locust in the swarm runs its own process and user can develop highly expressive Python scenarios without compromising the code with callbacks.</li><li>This means that this tool is entirely event-based, making it possible to support thousands of users from a single system.</li></ul><h3>Pros and Cons of Locust</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ojPg_DHg-dz2kDob6QMzQg.png" /></figure><h3><strong>Locust Vs JMeter</strong></h3><p>Let’s take a look at this comparison table of JMeter and Locust features and abilities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*aAmk7sjU_2Ok7yqeiIJtnQ.png" /></figure><h3>Set up Locust on Windows</h3><p><strong><em>Step 1</em></strong> : <a href="#https://www.python.org/downloads/">Install Python</a> 3.6 or later</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*81HJJrMWutVT06VU6N6alw.png" /></figure><p><strong><em>Step 2 </em></strong>: Make sure that Python is added to Path variable under Environment Variables &gt; System Variables.</p><p><strong><em>Step 3</em></strong> : Validate that Python is installed successfully.</p><pre><strong>$ </strong>python --version</pre><p><strong><em>Step 4</em></strong>: Install Locust using pip</p><pre><strong>$ </strong>pip3 install locust</pre><p><strong><em>Step 5</em></strong> : Validate that Locust in installed successfully</p><pre>$ locust --version</pre><h3>First code with Locust</h3><p>Assume that your API is as below;</p><p><strong>API</strong> : &lt;baseURL&gt;/api/vi/token<br><strong>Json Body</strong> : {“applicationCode”: “abc” , “applicationSecret” : “xyz”}<br><strong>Method</strong> : POST</p><p>Then, simple Python code for above will be as follow;</p><pre>import time<br>from locust import HttpUser, task, between</pre><pre>class QuickstartUser(HttpUser):<br>    wait_time = between(1, 2.5)</pre><pre>@task<br>def on_start(self):<br>        self.client.post(&quot;/api/v1/token&quot;, json={&quot;applicationCode&quot;:&quot;abc&quot;, &quot;applicationSecret&quot;:&quot;xyz&quot;})</pre><p><strong><em>Step 1</em></strong>: Add the code to a Notepad++as above example and save it as ‘locustfile.py’ to your local directory.</p><p><strong><em>Step 2</em></strong>: Start Locust</p><pre>$ locust</pre><p><strong><em>Step 3</em></strong>: Validate below output</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zM9LgezeRqQH6jqgih8Nnw.png" /></figure><h3>Running Locust via Web UI</h3><p>As I have described in the previous section, once you have added the above code and started the Locust, then;<br><strong><em>Step 1</em></strong> : Open up a browser and enter the following URL</p><pre><a href="http://localhost:8089/">localhost:8089/</a></pre><p><strong><em>Step 2</em></strong>: You will get the below window. Fill the fields as required and click on ‘Start swarming’ button once you’re ready.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTOms3X65BoBWGxLsXfcEA.png" /></figure><p>The process will start and you will get a window containing Statistics, Charts, Failures, Exceptions and Download Data Tabs.</p><p>Navigate to the<strong><em> Statistics </em></strong>tab and you should see the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fAAw-pP5APFtvfuIKa5PkA.png" /></figure><p>Navigate to the<strong><em> Chart</em></strong> tab and you should see the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pGxNvJj-zhVPyjfpJ0CSQw.png" /><figcaption>Total Requests per Second</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HTsbsXb8ftSBWcZJ6Es5Qg.png" /><figcaption>Response Times (ms)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKFf2WjdedjJvB9lWL4zuA.png" /><figcaption>Number of Users</figcaption></figure><ul><li>You can notice that the RPS is quite low here. This is mainly because we have set the wait_time to be between 1and 2.5 seconds.</li><li>If you are required to do an actual actual load testing, feel free to change both of the values to 0. Restart your test and you should be able to see the maximum RPS that your server can handle.</li><li>According to your preferences and requirements, you can do experiment using a different number of users and hatch rate.</li></ul><h3>Running Locust via Command Line Interface</h3><p>Locust gives us the benefit of running the load test via the command line interface as well.</p><p>Add the --headless parameter with host, number of clients and hatch rate.</p><pre>$ locust -f locustfile.py --headless --host &lt;base URL&gt; -u 10 -r 10</pre><ul><li>-u → no. of users to spawn</li><li>-r → spawn / hatch rate</li><li>-t→ Stop after the specific amount of time</li><li>-csv → Save the result to files in CSV format</li><li>-locust --help → List down all the available parameters</li></ul><p>You will get the output as below;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQQODplPrKfXq-XmYhlwMQ.png" /></figure><h3>Conclusion</h3><ul><li>Nowadays there is a trend in industry that moving away from tradition load testing approaches to code-to-test approach by switching to tools like Locust.</li><li>Locust was created to solve some specific issues of current existing performance tools, but it also has both pros and cons.</li><li>In Locust, client behavior can be entirely specified by the user by using regular python. Therefore it’s highly flexible tool and also supports running load tests distributed across multiple machines.</li><li>We need to have a basic Python knowledge to work with Locust. So that, required technical skill set is bit more high than using none-code tools.</li></ul><blockquote>Based on the pros and cons of the Tools, our purpose and our scope of performance/load/stress testing , we can choose a tool as we preferred. But as in line with how industry goes, it would be an advantage for us to learn a modern performance testing tool like Locust.</blockquote><h3><strong>References</strong></h3><p><a href="https://dev.to/ajeebkp23/locust-an-open-source-load-testing-tool-5adb">https://dev.to/ajeebkp23/locust-an-open-source-load-testing-tool-5adb</a></p><ul><li><a href="https://docs.locust.io/en/stable/">Locust Documentation - Locust 2.14.2 documentation</a></li><li><a href="https://www.blazemeter.com/blog/jmeter-vs-locust-which-one-should-you-choose">JMeter vs. Locust - Which One Should You Choose? | BlazeMeter</a></li><li><a href="https://simpleprogrammer.com/load-testing-locust-framework/">What&#39;s Load Testing and How Does a Locust Framework Help? - Simple Programmer</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fc4054cce02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Google Tests Software]]></title>
            <link>https://dilushakumarage.medium.com/how-google-tests-software-b5b7b999ccfa?source=rss-fe34b10a2a82------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5b7b999ccfa</guid>
            <category><![CDATA[test-engineering]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[google-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[quality-engineering]]></category>
            <dc:creator><![CDATA[Dilusha Rasangi Kumarage]]></dc:creator>
            <pubDate>Tue, 04 May 2021 08:23:02 GMT</pubDate>
            <atom:updated>2021-05-04T08:23:02.325Z</atom:updated>
            <content:encoded><![CDATA[<p>Google was founded in September 1998 by <a href="https://en.wikipedia.org/wiki/Larry_Page">Larry Page</a> and <a href="https://en.wikipedia.org/wiki/Sergey_Brin">Sergey Brin</a> and back then same as initial stages of the other Software Companies, Google also used traditional processes of software testing.<br>But, with the rapidly growth of the Company, they learnt some lessons from traditional processes and innovated new processes of Software Testing.</p><p>As Google is one of the most successful software companies in the world, let’s see the lessons they learnt and Innovative techniques they use for software testing and how could we apply those processes and techniques to improve ourselves in software testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RzE9bch1mluXTSoAZBBayQ.jpeg" /><figcaption>Reference : <a href="https://www.mammoth-ai.com/mammoth-ai/software-testing-trends-top-7-to-look-for-in-2020/">https://www.mammoth-ai.com/mammoth-ai/software-testing-trends-top-7-to-look-for-in-2020/</a></figcaption></figure><p>We will go through the following;</p><ol><li><a href="#a3af">Some lessons from initial Google’s QA</a></li><li><a href="#5df0">Testing at Google</a></li><li><a href="#a6ae">Engineering Roles</a></li><li><a href="#0044">Crawl, Walk, Run Approach</a></li><li><a href="#b685">Testing on the Toilet (TotT) Concept</a></li><li><a href="#aba4">Fixing Test Hour Glass</a></li><li><a href="#af9b">Flaky Tests at Google</a></li><li><a href="#a50c">Few Catchy Statements found in the Book ‘How Google Tests Software’</a></li><li><a href="#81ed">Conclusion</a></li><li><a href="#6e1b">Recommendations</a></li></ol><h3>Some lessons from initial Google’s QA</h3><ul><li>In early stages, team relied heavily on manual operations and only a small handful of software engineers focused on building, testing and releasing software.</li><li>As Google grew, lengthy manual test cycles delayed feature launches.</li><li>Identifying bugs later in the development cycle took longer and longer time to fix them.</li><li>Therefore, they <strong><em>determined that pushing testing upstream via automation</em></strong> would help address these issues and quicken velocity.</li></ul><h3>Testing at Google</h3><p>Google considers 3 main important areas during Testing and I like to call them as “<strong>3 Gears</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*XbDAqXkDnXo3pHU85nq8tw.png" /><figcaption>3 Gears of Success</figcaption></figure><p><strong><em>Think Small and Fast</em></strong></p><ul><li>Favors “<a href="#0044">small, frequent releases</a>” and small, concise tests.</li><li>Instead of releasing new updates / features in large releases, tries to release as soon as they provide some benefit to the user, get feedback and reiterate as fast as possible.</li><li>Invest heavily in Unit and Integration Testing and use end-to-end testing more sparingly.</li><li>Googlers are encouraged to look for ways to speed up testing cycles and minimize test failures.</li></ul><p><strong><em>Software Testing is a Focus, Not a Team</em></strong></p><ul><li>Initially Software Engineers used to test their own code, but with the growth of the team, they identified the obstacles in it.</li><li>Next, instead of rolling out a traditional testing team, they started creating specialized Engineering roles with different Testing Focuses.<br>(This will be further discussed in the section “<a href="#a6ae">Engineering Roles</a>”)</li></ul><p><strong><em>Communicate Effectively</em></strong></p><ul><li>Engineers who focus on testing aren’t isolated in their own areas of Google’s offices, but are integrated with the rest of the engineering team.</li><li>Google also prominence on communicating product quality internally to increase ownership and outgrow the team to focus on quality every day. <br> → They internally publish data about code coverage which help increase adoption of best practices.<br> →Practice “<a href="#b685">Testing on the Toilet</a>’’ Method to foster a Culture of Quality Ownership.</li></ul><h3>Engineering Roles</h3><p>In most of the Software Companies, Test Engineers usually focus on the law hanging fruit, where they concern on Manual / Automated UI Testing Only.</p><p>Google blends development and testing together in order to prevent bugs in quality instead of trying to catch them later when it is more expensive and harder to fix.</p><blockquote>Google has a saying “<strong>You build it, You break it</strong>”.</blockquote><p>They have essentially 3 Engineering roles / Focus Groups;</p><p>1. <strong>Software Engineers (SWEs)</strong>who focus on write code, design architecture and documentation and do unit testing in their code.<br>2. <strong>Software Engineers in Test (SETs) </strong>who focus on testability, improve the code in Performance and security wise since they are responsible for quality of the feature, refactor code and write Automated unit testing frameworks.<br>3. <strong>Test Engineers (TEs)</strong> who focus on User Testing by thinking in End User Perspective, Test with their knowledge of Domain / Product expertise and Automate API &amp; UI Test Features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9VjZz6O1XWxYdw2yfw9wbw.png" /><figcaption>Engineering Roles</figcaption></figure><h3>Crawl, Walk, Run Approach</h3><p>One of the key ways that Google achieves good results with fewer testers than many companies is that they rarely attempt to release a large set of features at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/227/1*T-BunLrBim3I_zf7r-xgPg.png" /></figure><p>Google builds the core of a product and release it in the <em>moment as it is useful to a large crowd as feasible</em>, then get their feedback and iterate. This gives the chance to run tests and experiment on their applications early and obtain feedback from real human beings.</p><blockquote><strong>Ex.</strong> from a Google blog : <strong>Gmail</strong> → A product that kept its beta tag for four years. That tag was our warning to users that it was still being perfected. We removed the beta tag only when we reached our goal of 99.99% uptime for a real user’s email data. <strong>Obviously, quality is a work in progress!</strong></blockquote><p>In order to get a feature out to production Google has <strong>5 Channels</strong> to get through &amp; All the Automation Suits run in each of these channels every day.</p><p>If a bug is found in the field, a tester can create a test that reproduces it and run it against builds in each channel to determine if a fix has already been implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*IfZ2ndSv6g9qBMcuQKJP0w.png" /><figcaption>5 Channels</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*A1xuB1AfoGGdva68WNLCww.png" /></figure><blockquote><strong><em>Dogfooding</em> → </strong>Internal adoption of software that is not yet released. The phrase “eating your own dogfood” is meant to convey the idea that if you make a product to sell to someone else, you should be willing to use it yourself to find out if it is any good.</blockquote><p>Google breaks down their types of testing into<strong> 3 broad categories</strong> that include both manual and automated testing.<br>1. <strong>Small Tests</strong> : Written &amp; Used by SWEs and SETs and Focus on Single Module.<br>2. <strong>Medium Tests</strong> : Written &amp; Used by SETs and Focus on Integration of two or more features . <br>3. <strong>Large Tests : </strong>Written &amp; Used by TEs and Focus on Real User Scenarios.</p><h3>Testing on the Toilet (TotT) Concept</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*LCt85fKpcnK6XsRZHFmYEQ.png" /><figcaption>Testing on the Toilet</figcaption></figure><ul><li>Sometimes it can be little bit hard for us to remind what we learnt or find some better solutions while writing a test code / fixing a code failure. <br>If we could happen to see the similar types of posts , tips where you can’t ignore , it goes in to our mind easily and inspire us rather than try to by heart or google the solutions.</li><li>That is where Google came across this secret concept in the year 2006 with a small band of volunteers who are passionate about software testing.</li><li>They started to write flyers about everything from dependency injection to code coverage and then regularly plaster the bathrooms in all over Google with each episode, almost 500 stalls worldwide.</li><li>This is one of the most effective ways to spread ideas, share important tricks and techniques, generate discussion and drive new internal tool adoption to educate yourself and the rest of your company.</li><li>This is basically share the best practices in all levels of testing thorough out the Company to inspire the Software Engineers &amp; Test Engineers .</li></ul><blockquote>Google wanted to spread this secret weapon<strong> ‘Testing on the Toilet’ Concept </strong>with the rest of the world and they are putting episodes on the below blog on a regular basis and providing PDFs. ‘<a href="https://testing.googleblog.com/2007/01/introducing-testing-on-toilet.html">https://testing.googleblog.com/2007/01/introducing-testing-on-toilet.html</a>’</blockquote><blockquote><strong>Ex</strong> :<a href="http://gowest.nilin.se/wp-content/uploads/2010/12/WhoTestsTheTests.pdf">http://gowest.nilin.se/wpcontent/uploads/2010/12/WhoTestsTheTests.pdf</a><br> <a href="https://www.flickr.com/photos/stevec77/2509234715/">https://www.flickr.com/photos/stevec77/2509234715/</a></blockquote><h3>Fixing Test Hour Glass</h3><p>As Google grew, often the shape of the Google test distribution became undesirable, either top heavy or like an hourglass.</p><ul><li>With the <strong>Ice-cream Cone Approach</strong>, it took more time for End-to-end Testing and then they converted to Hour Glass Approach.</li><li>Later, Release cycles were becoming even shorter, CI/CD and micro services were becoming a trend and then, <strong>Hour Glass Approach</strong> of testing also didn’t support this at all.</li><li>Due to less time for run thousands of Unit and Integrations Tests compared to manage huge UI Tests and could find the bugs in earlier stages rather waiting till UI stage, Google Tests converted to <strong>Pyramid Approach</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*LO6rrKOEvGUMvIqHrKj_qA.png" /><figcaption>Evolution of Test Pyramid</figcaption></figure><blockquote>At a glance, following chart gives you a good understanding of <strong>Benefits of Test Pyramid Approach</strong> ahead Traditional (Ice-cream Cone) Approach.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*569nVJx1s8XHz6WSm3BWpw.png" /></figure><h3>Flaky Tests at Google</h3><p><strong><em>What is a Flaky Test ?</em></strong></p><p>Flaky test is a test that both passes and fails periodically without any <br>code changes. Initially Google found out that almost 16% of their tests have some level of flakiness associated with them.</p><p>This is one of the main challenges in Automated Testing and The goal of a good test suite is to make this signal as clear and directed as possible.</p><p><strong><em>What are the Reasons of Test Flakiness?</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTyE4EfQ3uJm3xvYBIk3Qg.png" /></figure><p><em>It was a main challenge for them to determine whether a new failure is a <br> flaky result or a legitimate failure.</em></p><p><strong><em>What are the Test flakiness Mitigation Plans at Google?</em></strong></p><ul><li>An option to re-run tests automatically when they fail &amp; Report a failure only if it fails 3 times in a row.</li><li>A tool that monitors the flakiness of tests and if the flakiness is too high, it automatically quarantines the test. Quarantining removes the test from the critical path and files a bug for developers to reduce the flakiness.</li><li>Another tool detects changes in the flakiness level of tests and works to identify the change that caused the test to change the level of flakiness.</li></ul><blockquote>Google has a new team dedicated to provide accurate &amp; timely information about test flakiness and analyze the data from flaky test executions.</blockquote><h3>Few Catchy Statements found in the Book ‘How Google Tests Software’</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tq6SDAhe52_DXLlEY92d9Q.png" /></figure><h3>Conclusion</h3><ul><li>Google has crafted their own <strong>process of moving fast</strong>. It’s a very Agile process that doesn’t get bogged down with someone else’s idea of what it means to be Agile.</li><li>Both <strong>Developers &amp; Testers</strong> think about the <strong>Quality of Product</strong> according to their Engineering Role (SWE, SWET &amp; TE) &amp; Focus.</li><li>They focus on <strong>break the features</strong> in to small chunks first, Code little &amp; test.</li><li>They do more Test on lower stages than higher stages by adhering to<strong> Test Pyramid </strong>Approach.</li><li>They don’t have specific manual testers &amp; <strong>Test Automation</strong> <strong>is a must </strong>in<strong> </strong>each level of Functional &amp; None Functional Testing.</li><li><strong>A Good Test Engineer</strong> is who is <strong>Technical and cares about the Product in UI Perspective as well</strong> as understand the product at a system and end-to-end perspective.</li></ul><h3>Recommendations</h3><ul><li><strong>I suggest that we can Implement Google ‘Testing on the Toilet’ Approach at other software companies too.<br> <br><em>Method 1</em></strong>: We can grab the PDF Versions of Google’s TotT episodes or create our own posters that are more relevant to the company and put them in places where both developers and testers can’t be ignored.<br><strong><em>Method 2 </em></strong>: We can initiate something called ‘<strong>Tip of the day’</strong> Mailing System from Quality Engineering Department.</li><li><strong>I Suggest that, we can start testing according to the new Test Pyramid Method &amp; Automate Tests in all levels of Testing.<br> (</strong>We can make an awareness of developers about this Pyramid as well<strong>)</strong></li><li><strong>Implement a Code Coverage Tool after the Unit Test with Quality Gates in possible Projects.</strong></li><li><strong>Apply Auto Retry for E2E UI Test Automation Suits to reduce the Test Flakiness.<br> Ex : </strong>npm — g protractor-retry</li></ul><blockquote><strong>As Test Engineers we all should try to be a Full stack Quality Engineers </strong>who<strong> </strong>will think about the many different aspects of product quality across all the application’s layers using different testing methods such as functionality, none-functionality (usability, performance, security etc. ) and will also be familiar with test automation strategies and technologies.</blockquote><h3>References</h3><p><strong>Google Testing Blogs</strong>: <br><a href="https://testing.googleblog.com/">https://testing.googleblog.com</a>/</p><p><strong>Articles on How Google Tests Software</strong> :</p><ul><li><a href="https://dzone.com/articles/what-growing-teams-can-learn-from-how-google-qa-te">What Growing Teams Can Learn From How Google QA Tests Software - DZone DevOps</a></li><li><a href="https://www.kenst.com/2011/04/summary-how-google-tests-software/">Summary: How Google Tests Software - Chris Kenst</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5b7b999ccfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>