<?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 Jia Le Yeoh on Medium]]></title>
        <description><![CDATA[Stories by Jia Le Yeoh on Medium]]></description>
        <link>https://medium.com/@Jia_Le_Yeoh?source=rss-cfe996f4781------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Jia Le Yeoh on Medium</title>
            <link>https://medium.com/@Jia_Le_Yeoh?source=rss-cfe996f4781------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:10:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Jia_Le_Yeoh/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[Performance Testing, Load Testing & Stress Testing]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/performance-testing-load-testing-stress-testing-39f7b1316a44?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/39f7b1316a44</guid>
            <category><![CDATA[stress-testing]]></category>
            <category><![CDATA[non-functional-testing]]></category>
            <category><![CDATA[performance-testing]]></category>
            <category><![CDATA[load-testing]]></category>
            <category><![CDATA[example]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Thu, 09 Dec 2021 11:35:39 GMT</pubDate>
            <atom:updated>2021-12-09T11:35:39.742Z</atom:updated>
            <content:encoded><![CDATA[<p>Non-Functional Testing of examples</p><p><strong>Example of Performance Test Cases</strong></p><ul><li>When 1000 users access the website at the same time, make sure the response time is less than 4 seconds.</li><li>When network connectivity is slow, check that the Application Under Load’s response time is within an acceptable range.</li><li>Before the application crashes, check the maximum number of users it can manage.</li><li>When 500 records are read/written at the same time, check the database execution time.</li><li>Check the application’s and database server’s CPU and memory utilization during high loads.</li><li>Check the application’s reaction time under low, medium, moderate, and heavy load circumstances.</li></ul><p>Vague words like acceptable range, heavy load, and so on are replaced by real values during the actual performance test execution. These metrics are set by performance engineers based on the application’s technological landscape and business requirements.</p><p><strong>Examples of performance testing</strong></p><p><strong>JMeter:</strong></p><p>JMeter is a graphical Java desktop application that makes use of the Swing graphical API. As a result, it can execute in any environment that supports the Java virtual machine. Overall, this is an open-source performance testing tool for doing load and performance tests. This aids in the analysis and measurement of a variety of web and web service applications.</p><p><strong>Load Runner:</strong></p><p>The HP load runner is a tool that allows you to test your applications under regular and peak load situations. The load runner creates virtual users that simulate network activity to produce load. It generates graphical results while simulating real-time usage in a production context.</p><p><strong>Example of Load Testing:</strong></p><ul><li>Transferring a huge number of papers for printing to test a printer</li><li>Thousands of concurrent users were used to test a mail server.</li><li>Making a modification in a big volume of data to test a word processor</li></ul><p><strong>Example of Stress Testing:</strong></p><ul><li>An extraordinarily large volume of visitors to the ecommerce application is replicated using a stress testing tool in order to undertake stress testing of the application (listed later in this article).</li><li>When compared to the typical number of users projected to visit the website on a daily basis, the number of visitors simulated would be exponentially higher.</li><li>These virtual users are designed to perform basic tasks such as inspecting products, adding, removing, and purchasing items from carts, among others.</li><li>The number of users is suddenly increased to the point of failure, till the website breaks and can no longer handle the extra load.</li><li>Additional considerations include how the website acts at this period and whether or not it recovers gracefully.</li><li>The test findings are used to identify bottlenecks, areas for performance improvement, recovery / failover procedures, and so on.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f7b1316a44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Explain the synchronization problem in Selenium]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/explain-the-synchronization-problem-in-selenium-cb89bbc128a?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb89bbc128a</guid>
            <category><![CDATA[explanation]]></category>
            <category><![CDATA[synchronization-problem]]></category>
            <category><![CDATA[selenium]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Fri, 01 Oct 2021 06:43:06 GMT</pubDate>
            <atom:updated>2021-10-01T06:43:06.096Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Synchronization problem in Selenium</strong></p><p>Because the Selenium WebDriver typically has to block APIs, and the web platform is asynchronous, it does not track the state of the DOM in real time.</p><p>When operations are done on a web element that is not yet present in the DOM or is not in a position to accept instructions, synchronization issues occur (e.g., not visible, not clickable, etc.).</p><p>When the user instructs the browser to travel to a specific page and the Selenium test automation implementation encounters an ElementNotVisibleException while trying to discover a web element, race situations are likely. Selenium’s wait commands can be used to prevent race circumstances between the browser and the Selenium WebDriver script.</p><p>Wait instructions in Selenium can be used to handle synchronization, such as waiting for a given duration or for a specific condition to occur.</p><p>For test automation, we used the PHPUnit framework. The test execution was successful on the first run, but the second run resulted in an ElementNotInteractableException. As a result, the test scenario’s behavior (i.e., whether it passes or raises “various types” of exceptions) cannot be predicted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/0*bfV9a-3RtempIqpt.png" /><figcaption><em>Successful test execution from </em><a href="https://www.lambdatest.com/blog/wp-content/uploads/2021/03/image1-5.png"><em>cite</em></a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*_rXdgqFhUMRCR4hx.png" /><figcaption><em>Test Execution resulting in ElementNotInteractableException from </em><a href="https://www.lambdatest.com/blog/wp-content/uploads/2021/03/image2-8-768x275.png"><em>cite</em></a></figcaption></figure><p>Because there is no guarantee about the web components or events that are triggered asynchronously, without stopping or explicitly waiting on those events, this Selenium WebDriver script may be intermittent. Wait commands in Selenium PHP come in helpful here because they aid with synchronization concerns in Selenium web automation.</p><p><strong>For example</strong>, the Implicit Wait command specifies a wait time of 30 seconds. The chosen time (30 seconds) is used as the default for all subsequent testSteps, resulting in execution time. Explicit waits were created to address this issue, and they are used to apply waits whenever they are required while running the testSteps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb89bbc128a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Different design patterns for automated tests]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/different-design-patterns-for-automated-tests-c2fb2557dc2e?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2fb2557dc2e</guid>
            <category><![CDATA[different-design]]></category>
            <category><![CDATA[different-design-patterns]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Thu, 30 Sep 2021 05:56:20 GMT</pubDate>
            <atom:updated>2021-09-30T05:56:20.270Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What are the different design patterns for automated tests?</strong></p><p>Three types of design patterns can be found:</p><p><strong>Structural patterns</strong> describe how to put items and classes together to form larger structures that are both flexible and efficient.</p><p>Object creation techniques are provided by <strong>creational patterns</strong>, which enable the flexibility and reuse of existing code.</p><p>Algorithms and the assignment of responsibility between objects are the focus of <strong>behavioral patterns</strong>.</p><p><strong>Structural design patterns</strong></p><p><strong>Page Object Models (POM): </strong>This is the most prevalent structural design pattern, and it’s often used to automate UI test cases in test automation frameworks. The pattern separates the actual testing from any page information.</p><p>POMs are advantageous because:</p><ul><li>There is no need for developers to write redundant code. They create page components (such as input fields and buttons) that are utilized to construct additional page elements.</li><li>Encapsulation and abstraction are provided by the pattern. Web components or other class members are encapsulated in page objects, which allow access to wrapper methods that mask all the code (i.e., the mechanics used to locate or change data).</li><li>By creating and structuring page objects, developers may better grasp the structure of the automation solution through usage, new test creations, page component development, and test readability.</li></ul><p>Page objects, also known as loadable components, are similar to interfaces for web pages or web page components. These elements should facilitate the same interaction with other web sites and include:</p><ul><li>web parts that are preferably contained</li><li>other objects on the page</li><li>By design, there are methods to work with page objects and return additional page objects.</li><li>On page objects, no assertions should be used.</li></ul><p>Follow a folder and file structure to organize and keep page items conveniently available while using POM. Depending on the methodology and need, page objects can be built in a functional or structural manner.</p><p><strong>Composite patterns</strong></p><p>To depict part-whole hierarchies, this pattern assembles objects into tree structures. Individual objects and object compositions can be treated evenly with composites.</p><p><strong>A composite design is advantageous for the following reasons:</strong></p><ul><li>Polymorphism and recursion are used to simplify the representation of complicated tree structure components as branches.</li><li>It’s simple to add new items to the structure without changing the code (the Open/Close principle).</li></ul><p>A collection of page items is built up to build a tree structure in automation solutions, resulting in composite patterns. While this is correct, the major purpose of a composite pattern is to treat individual objects and object combinations in a consistent manner. The structure allows the client control over the component interface by abstracting it.</p><p>Engineers utilize a composite pattern to develop components that benefit from a tree structure (e.g., menus that require sub-menus, sub-sub-menus, and so on) in order to retrieve, select, or print all of the elements using recursion. Include custom iterators for more sophisticated requirements.</p><p><strong>Creational design patterns</strong></p><p><strong>Factory method patterns</strong></p><p>This pattern defines an object creation interface, but subclasses can choose which class to instantiate. Subclasses can use factory methods to defer creation.</p><p><strong>A factory method pattern is useful because it allows you to:</strong></p><ul><li>Having all of the objects’ initialization in one location makes later support a lot easier (Single Responsibility Principle).</li><li>The pattern (for example, the open/close principle) can be simply extended without modifying current code.</li><li>For test runs, scalability is simple to manage (e.g., using Selenium Grid/ Docker containers).</li></ul><p>A factory method pattern is a creational pattern for encapsulating concrete type instantiation while avoiding tight coupling between the creator and concrete products. To extend the codebase, engineers do not need to change any code.</p><p>The Selenium WebDriver initialization is one of the best instances of a test automation framework. When all Webdrivers share the same “IWebDriver” interface, refer Webdrivers through that interface, even if most initializations require some form of configuration thereafter. It’s simple to add another Webdriver if necessary. Simply extend the factory method, which does not require any code changes.</p><p>PageFactory is a built-in factory method in the Webdriver that is responsible for all page element initialization. Declare the web elements and, if necessary, offer additional properties.</p><p><strong>Singleton patterns</strong></p><p>This pattern ensures that a class only has one instance and gives a single point of access for all instances.</p><p><strong>A singleton pattern is advantageous for the following reasons:</strong></p><ul><li>A single instance of an object exists. The design is most commonly used for Logger, Connections, and External Resources.</li><li>A global access point to a class instance is required by developers.</li></ul><p><strong>Behavioral design patterns</strong></p><p><strong>Strategy patterns</strong></p><p>This pattern describes a set of algorithms, encapsulates them, and allows them to be swapped out. The algorithm can alter independently of the clients who utilize it thanks to strategy patterns.</p><p><strong>A strategy pattern is advantageous because it:</strong></p><ul><li>Engineers use a variety of algorithms to finish a task, which can change based on the task at hand.</li><li>The Open/Close paradigm allows developers to simply add new strategies without changing the code.</li></ul><p>Strategy patterns are useful in a variety of disciplines in test automation. <strong>For example</strong>, on a checkout page, an application may feature multiple payment methods/a different implementation of the same task, such as account creation. One approach makes use of user interfaces, while the other makes use of RESTful calls.</p><p>These algorithms (strategies) are simple to create, encapsulate, and apply to a variety of situations. Engineers remove all logic from page objects and allow them to delegate all work to strategy objects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2fb2557dc2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do we need design pattern in our automated test suite?]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/why-do-we-need-design-pattern-in-our-automated-test-suite-5e94da7263e?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e94da7263e</guid>
            <category><![CDATA[need]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[automated-test]]></category>
            <category><![CDATA[automated-test-suite]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Wed, 29 Sep 2021 05:11:48 GMT</pubDate>
            <atom:updated>2021-09-29T05:11:48.168Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Why do we need design pattern in our automated test suite?</strong></p><p><strong>Design patterns: suitable software testing method</strong></p><p>During the development of an application, developers must fix problems as they arise. There’s a strong probability that someone else has already addressed the same or a similar problem. Design patterns offer a generic, reusable answer to frequent difficulties in software development. Design patterns are similar to best practices collections in that they provide an idea but not specific implementations. Design patterns make programs more extendable and manageable by reducing code complexity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e94da7263e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Page Object Model]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/page-object-model-b807fc98ceeb?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/b807fc98ceeb</guid>
            <category><![CDATA[test-case]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[test-scripts]]></category>
            <category><![CDATA[page-object-model]]></category>
            <category><![CDATA[pages]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Wed, 29 Sep 2021 04:10:12 GMT</pubDate>
            <atom:updated>2021-09-29T04:10:12.211Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is page object model?</strong></p><p>The Page Object Model, or POM, is a Selenium design pattern that builds an object repository to store all web elements. It aids in the reduction of code duplication and the maintenance of test cases.</p><p>Consider each web page of an application as a class file in the Page Object Model. Each class file will only contain web page components that pertain to it. Testers can use these items to conduct operations on the website under test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hHtqxH-HTu8ukgfN.png" /><figcaption>Original Picture from <a href="https://www.toolsqa.com/gallery/selnium%20webdriver/1.Page%20Object%20Model%20Project%20Structure.png">cite</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b807fc98ceeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Pattern]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/design-pattern-d8b16b5f3505?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8b16b5f3505</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[software-design-patterns]]></category>
            <category><![CDATA[software-design]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Wed, 29 Sep 2021 03:59:57 GMT</pubDate>
            <atom:updated>2021-09-29T03:59:57.694Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is a design pattern?</strong></p><p>A design pattern is a generic, reusable solution to a problem that arises frequently in software development. The pattern usually depicts the interactions and links between classes or items. The goal is to make the development process go faster by providing tried-and-true development/design paradigms. Design patterns are problem-solving methodologies that are independent of programming languages. A design pattern, thus, represents an idea rather than a specific implementation. You may make your code more flexible, reusable, and maintained by employing design patterns.</p><p>It is not necessary to use design patterns in all of your projects. Design patterns aren’t supposed to be used in the development of projects. Design patterns are used to solve common problems. You must adopt a suitable pattern whenever a need arises in order to avoid future difficulties. To figure out which pattern to utilize, all you have to do is try to comprehend design patterns and their functions. You will only be able to choose the proper one if you do so.</p><p>The goal is to understand the purpose and application of each design pattern so that you can select and implement the appropriate pattern as needed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8b16b5f3505" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IWebDriver and IWebElement]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/iwebdriver-and-iwebelement-51139142cb9f?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/51139142cb9f</guid>
            <category><![CDATA[iwebdriver]]></category>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[iwebelement]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Mon, 27 Sep 2021 06:49:51 GMT</pubDate>
            <atom:updated>2021-09-27T06:49:51.731Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is IWebDriver and IWebElement?</strong></p><p><strong>IWebDriver</strong></p><p>Defines the user’s interface for controlling the browser.</p><p>The IWebDriver interface, which represents an idealized web browser, is the key interface to utilize for testing. There are three types of methods in this class:</p><ul><li>Control over the web browser</li><li>IWebElements Selection</li><li>Aids for debugging</li></ul><p>Url, which is used to load a new web page by setting the property, and the different methods comparable to FindElement(By), which are used to find IWebElements, are important properties and methods.</p><p><strong>IWebElement</strong></p><p>An HTML element is represented by WebElement. HTML elements are the building blocks of HTML documents. A start tag, an end tag, and the content in between are used to create HTML elements: &lt;tagname&gt; content &lt;/tagname&gt;</p><p>Everything from the start tag to the end tag is considered an HTML element:&lt;p&gt; My first HTML paragraph. &lt;/p&gt;</p><p>HTML elements can be nested, which means they can be stacked on top of each other (elements can contain elements). Nested HTML elements can be found in any HTML document.</p><p><strong>Example:</strong></p><pre>&lt;html&gt;<br>	&lt;body&gt;<br>		&lt;h1&gt; My First Heading &lt;/h1&gt;<br>		&lt;p&gt; My first paragraph. &lt;/p&gt;<br>	&lt;/body&gt;<br>&lt;/html&gt;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51139142cb9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How often do you run your automated test cases?]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/how-often-do-you-run-your-automated-test-cases-80ba1d99c561?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/80ba1d99c561</guid>
            <category><![CDATA[automated-test-cases]]></category>
            <category><![CDATA[how-long-does-it-take]]></category>
            <category><![CDATA[run-automated-testing]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[how-often-do-you-run]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Mon, 27 Sep 2021 04:52:52 GMT</pubDate>
            <atom:updated>2021-09-27T04:53:06.470Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How often do you run your automated test cases?</strong></p><p>If they can be operated unsupervised, do it every week over the weekend. This will provide you with adequate run-time and a sufficient pause between runs to address errors and possibly improve the automation.</p><p>The analysis of the results, on the other hand, is a different matter. You have found that categorizing the results into characteristics/categories is helpful. That way, You can rapidly identify the most serious issues in the data collection and concentrate your efforts there.</p><p>When it comes to dealing with problems, it all depends on the quality of the provided result as well as the bug’s kind. There should be more to the results than just pass/fail. The applicable error message, test action and parameters, and version information should all be included. This allows them to be readily transformed into bugs. If that isn’t possible, they can be readily replicated manually and reported as problems that way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80ba1d99c561" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who executes the automated test cases?]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/who-executes-the-automated-test-cases-5b9a48a4ef94?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b9a48a4ef94</guid>
            <category><![CDATA[automated-test-cases]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[execute-test-cases]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Sun, 26 Sep 2021 05:26:41 GMT</pubDate>
            <atom:updated>2021-09-26T05:26:41.236Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Who executes the automated test cases?</strong></p><p>The Automated Test Team/QA Team will execute the automated test cases.</p><p>The execution plan and how the QA team implements it are crucial to the effectiveness of automation testing. Here are some things that any automation testing beginner should know before building their first script.</p><p><strong>Choose a suitable execution environment</strong><br>What is an execution environment, exactly? Before generating the first test case, this is the most important question to answer. The phrase “execution environment” refers to all of the components that operate together with the application’s code to create a full and functional system, such as processors, networks, and operating systems.</p><p>The most important part of the testing process is the execution environment. It entails hardware and software configuration, operating system settings, test terminals, and other test-related assistance.</p><p><strong>Integrate tools into the framework for automated testing</strong><br>Before continuing, it’s important to note that your tools must be integrated with the test framework. The framework should already include your preferred tools from earlier levels.</p><p>Examine your tools to see if there are any compatibility issues or poor linking. Check that open-source tools operate well with commercial parent tools, <strong>for example</strong>.</p><p><strong>Create and improve automation scripts</strong><br>Some test engineers like to start the test process by drafting automation scripts that can be used for most test cases. The scripts are then refined in the execution phase using an iterative method in a highly collaborative cloud environment.</p><p><strong>Execute the automation</strong><br>At this point in the journey, it’s best to prioritize quality over number when it comes to test automation. Create a smaller number of working automated test cases instead of a huge number that will need to be discarded or changed later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b9a48a4ef94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you choose which test case to automate?]]></title>
            <link>https://medium.com/@Jia_Le_Yeoh/how-do-you-choose-which-test-case-to-automate-d5c7fbe49aae?source=rss-cfe996f4781------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5c7fbe49aae</guid>
            <category><![CDATA[test-case]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Jia Le Yeoh]]></dc:creator>
            <pubDate>Sat, 25 Sep 2021 09:42:21 GMT</pubDate>
            <atom:updated>2021-09-25T09:42:21.853Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How do you choose which test case to automate?</strong></p><p><strong>Analyzing on the right test cases for test automation</strong></p><p>A thorough discussion of the testing requirements and the testers’ abilities will go a long way toward ensuring that the Automation testing produces the required results.</p><p>The following are the <strong>most important considerations while selecting automation test cases</strong>:</p><ul><li>Test Frequency</li><li>Resources Requirements</li><li>Execution Time</li><li>Human error is possible.</li><li>The Downside of Automation is that it does not compromise on ROI.</li></ul><p><strong>Execution Time:</strong> If you believe the test case will take longer to complete manually, automation testing is the way to go. We’ll be able to use our testers more efficiently this way. We can also handle massive data sets with a small team of testers.</p><p><strong>Test Frequency:</strong> Automation testing is the best alternative when we need to repeat the test frequently. Regression tests are essential for automation testing since we must execute them with every application we build.</p><p>OS, Browsers, Devices, and Databases are examples of <strong>resource requirements</strong>. The level of user interaction necessary in the test will determine whether or not test cases should be automated. The higher the level of engagement, the less likely it is to be automated.</p><p><strong>Subject to Human Error:</strong> When we believe that executing the test manually will result in considerable Human error, we can add those test cases in the test suite for automated testing to improve the quality of the tests and reduce time spent on them.</p><p><strong>The Disadvantages of Not Sacrificing ROI for Automation: </strong>Automation testing has a number of drawbacks, including high implementation costs, ongoing maintenance costs, and the need for human interaction. The time, insights, and human resources saved are all factors in the value of ROI. It qualifies for the relevant test cases for automation testing when the value (ROI) surpasses the negative.</p><p><strong>Complex Cases:</strong></p><p>Complex test scenarios are virtually always automated. When it comes to intricacy, you always want to stay on the safe side and save time.</p><p><strong>Long Testing:</strong></p><p>If a situation necessitates nightly devotion, it should be automated.</p><p><strong>Extensive Tests:</strong></p><p>It can be exhausting to enter a large amount of data. Furthermore, the likelihood of making a mistake during manual testing increases. This is why most tests involving large data sets are automated. Specifically, we’re talking about test scenarios that need you to complete out lengthy forms.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5c7fbe49aae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>