<?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 Dilkushi Jayaweera on Medium]]></title>
        <description><![CDATA[Stories by Dilkushi Jayaweera on Medium]]></description>
        <link>https://medium.com/@dilkushi.j?source=rss-d7321c2f3d6a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KhLBlQqCO_wegEyNStW_Ew.jpeg</url>
            <title>Stories by Dilkushi Jayaweera on Medium</title>
            <link>https://medium.com/@dilkushi.j?source=rss-d7321c2f3d6a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:39:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dilkushi.j/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[Cypress Framework — Beginner Guide]]></title>
            <link>https://medium.com/@dilkushi.j/cypress-framework-beginner-guide-9250708a0ebc?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9250708a0ebc</guid>
            <category><![CDATA[cypress-automation]]></category>
            <category><![CDATA[cypress-for-beginner]]></category>
            <category><![CDATA[cypress-framework]]></category>
            <category><![CDATA[cypress-testing]]></category>
            <category><![CDATA[cypress]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Wed, 12 Jun 2024 21:54:59 GMT</pubDate>
            <atom:updated>2024-06-17T11:58:55.947Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cypress Framework -Beginner Guide</h3><p>If you are fresher wondering where to begin with cypress tests, this is for you. Let’s get familiarise with the cypress framework, before writing tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVZKirSEcdbNLP9ieW2W5Q.jpeg" /></figure><p>In this blog we are going to cover:</p><ol><li><strong>Cypress Folder Structure</strong></li><li><strong>Cypress Runner</strong></li><li><strong>Cypress Commands</strong></li><li><strong>Element Selectors</strong></li><li><strong>Cypress Assertions</strong></li></ol><h4><strong>1. Cypress Folder Structure</strong></h4><p>Let’s look at the folder structure of cypress. The general structure of a Cypress project as you install it, as follows.</p><p><strong>my-cypress-project/<br>├── cypress/<br>│ ├── fixtures/<br>│ │ └── example.json<br>│ ├── integration/<br>│ │ └── examples/<br>│ │ └── actions.spec.js<br>│ ├── plugins/<br>│ │ └── index.js<br>│ ├── support/<br>│ │ ├── commands.js<br>│ │ └── index.js<br>├── cypress.config.json<br>├── package.json<br>└── package-lock.json</strong></p><ol><li><strong>Cypress</strong></li></ol><p>The main directory for all Cypress-related files.</p><p><strong>2. Fixtures</strong></p><p>Contains test data in the form of JSON files. These files can be used to mock API responses or provide data for your tests.</p><p><strong>3. Integration</strong></p><p>This folder contains your test files (also known as spec files). This is where you’ll write tests that interact with your application through a browser.</p><p><strong>4. Plugins</strong></p><p>This folder is used to extend or modify the internal behavior of Cypress. You can use plugins to customize how Cypress works.</p><p><strong>5. Support</strong></p><p>This folder contains files that run before and after each test file. Contains reusable behavior or custom commands that can be used across your tests.</p><ul><li><strong><em>commands.js</em></strong> : A file to define custom commands.</li><li><strong><em>index.js</em></strong> : A file that runs before every single spec file and is a great place to put global configuration and behavior modifications.</li></ul><p><strong>6. Cypress.config.json</strong></p><p>The main configuration file for Cypress. This JSON file is used to set various options, such as baseUrl, integrationFolder, etc.</p><p><strong>7. Package.json</strong></p><p>The package. json file is the heart of any Node project. It defines functional attributes of a project that npm uses to install dependencies, run scripts, and identify the entry point to our package. When you install Cypress, it gets added as a dependency here.</p><p><strong>8. Package-lock.json</strong></p><p>Package-lock. json goes a step further by resolving and documenting the precise dependencies, sub-dependencies, and installation paths for accurate reproducibility.</p><h3>2. Cypress Runner</h3><p>Cypress runner is a test runner for the Cypress testing framework. It provides a graphical user interface (GUI) and a command line interface (CLI) for running Cypress tests in a browser environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgqYtCREDAERYSFtI93qYQ.png" /></figure><p>The Cypress runner allows developers to run and debug their tests in real time, view the results, and interact with their application as if they were a real user. It also provides features such as test reordering, parallelisation, and test recording.</p><h3>3. Cypress Commands</h3><p>Cypress comes with an in-built set of commands to interact with the web page, perform actions, and make assertions.</p><p>There are there types of cypress commands.</p><ol><li><strong><em>Parent commands</em></strong></li><li><strong><em>Child commands</em></strong></li><li><strong><em>Dual commands</em></strong></li></ol><h4>Parent commands</h4><p>Parent commands begin with a new chain of cypress commands.</p><ul><li><strong><em>cy.visit()</em>:<em> </em></strong>Navigate to a specific URL in your application.</li><li><strong><em>cy.get()</em>:</strong> Retrieves an element or a set of elements from the DOM.</li><li><strong><em>cy.contains()</em>:</strong> Retrieves a set of elements that contain a specific text content.</li></ul><h4>Child commands</h4><p>Child commands are always chained off of a parent command or another child command.</p><ul><li><strong><em>.find(selector)</em>:</strong> Gets descendant DOM elements of the selector.</li><li><strong><em>.click()</em></strong>: Clicks on a DOM element.</li><li><strong><em>.type(text)</em></strong>: Types into a DOM element.</li></ul><h4>Dual commands</h4><p>Dual commands can act as either a parent command or a child command. They can start a new chain or be chained off of an existing command.</p><ul><li><strong><em>cy.contains(text)</em></strong>: Finds a DOM element containing the specified text.</li><li><strong><em>cy.screenshot()</em></strong>: Takes a screenshot of the current viewport or a specified element.</li></ul><h4><strong><em>- Key Features of Cypress Commands -</em></strong></h4><ul><li><strong>Chain-able Syntax</strong>:</li></ul><p>Cypress commands are designed to be chained, which improves readability and maintainability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04mszeQgiYheh7bzag0dwQ.png" /></figure><ul><li><strong>Built-in Assertions</strong>:</li></ul><p>Many Cypress commands come with built-in assertions, which makes the test code more concise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0e8L-YIke5bQep92ILYwKA.png" /></figure><ul><li><strong>Custom Commands</strong>:</li></ul><p>You can define your own custom commands to encapsulate reusable logic, making your tests more reusable.</p><ul><li><strong>Automatic Waiting</strong>:</li></ul><p>Cypress automatically waits for commands and assertions to complete before moving on to the next command. This eliminates the need for explicit waits or sleep commands in most cases.</p><ul><li><strong>Retry Logic</strong>:</li></ul><p>Cypress commands automatically retry until they succeed or a timeout is reached. This is particularly useful for elements that may not be immediately available or for asynchronous operations.</p><h3>4. Element Selectors</h3><p>Element selectors in Cypress are used to identify and interact with elements on a web page during tests. Using the right selectors is a must for writing robust and maintainable tests.</p><p>Cypress supports a variety of selector strategies, allowing you to target elements in multiple ways.</p><h4>Types of Element Selectors</h4><ol><li><strong><em>CSS Selectors</em></strong></li><li><strong><em>Attribute Selectors</em></strong></li><li><strong><em>Text Selectors</em></strong></li><li><strong><em>XPath Selectors</em></strong></li><li><strong><em>Custom Commands</em></strong></li></ol><h3>5. Assertions in Cypress</h3><p>Assertions in Cypress are used to verify that the application is behaving as expected.</p><h4>Types of Assertions</h4><ol><li><strong>Implicit Assertions</strong></li><li><strong>Explicit Assertions</strong></li></ol><p>They help ensure that elements are present, have the correct properties, and that actions produce the expected results.</p><p>Eg:</p><ul><li><strong><em>should(‘be.visible’)</em></strong>: Asserts that the element is visible.</li><li><strong><em>should(‘contain’, text)</em></strong>: Asserts that element contains the specified text.</li><li><strong><em>should(‘be.disabled’)</em></strong>: Asserts that the element is disabled.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bGTpn0hFghab8Vc-0XyUNw.png" /></figure><p><em>If you like this article, please show your support clicking the clap button below and follow for more. Thank you! </em><strong>😊👍</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9250708a0ebc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating a Quill Text-Editor in Cypress]]></title>
            <link>https://medium.com/@dilkushi.j/automating-a-quill-text-editor-in-cypress-f7e3a2d2f2da?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7e3a2d2f2da</guid>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Thu, 14 Mar 2024 21:31:59 GMT</pubDate>
            <atom:updated>2024-03-14T21:31:59.104Z</atom:updated>
            <content:encoded><![CDATA[<p>Quill is a modern open-source text editor designed for web applications. It’s often used to provide rich text editing capabilities within web applications, allowing users to format text, insert images, create links, and more.</p><p>Quill is built with JavaScript and offers a flexible API that developers can use to customize its behavior and appearance to suit their specific needs. It’s designed to be lightweight, fast, and easy to integrate into web projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mRiAFMUDVR-wd7HKaa5byQ.png" /><figcaption>Quill Text-Editor</figcaption></figure><p><strong><em>Some key features of Quill include:</em></strong></p><ol><li>Rich text editing: Quill allows users to format text using familiar tools like bold, italics, underline, bullet points, and headings.</li><li>Embeddable media: Users can insert images, videos, and other media directly into their documents.</li><li>Customizable toolbar: Developers can customize the toolbar to include only the formatting options they want to provide to users.</li><li>Cross-browser compatibility: Quill works across major web browsers, ensuring a consistent editing experience for users.</li><li>Modular architecture: Quill’s architecture is modular, making it easy to extend and customize with plugins.</li></ol><p>It provides a convenient solution for implementing rich text editing functionality in web applications, making it popular among developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*yodMJhJnt12TwzLuBZ14UQ.jpeg" /></figure><p><em>When automating Quill for testing purposes, integration with testing frameworks like Cypress or Selenium may require additional considerations compared to automating a plain text editor</em>.</p><p><strong>Enter text to a Quill Text-Editor using Cypress</strong></p><pre>cy.get(elementSelector).should(&#39;be.visible&#39;).then(($quillContainer) =&gt; {<br>    // Attempt to find the Quill editor within the container<br>    const quillEditor = $quillContainer.find(&#39;.ql-editor&#39;)[0];<br><br>    if (quillEditor) {<br>      // Use Quill&#39;s API to set content<br>      cy.wrap(quillEditor).type(value);<br>    } else {<br>      // Handle the case when Quill editor is not found<br>      throw new Error(&#39;Quill editor not found within the selected element&#39;);<br>    }<br>  });</pre><p><strong>Upload an image into the Quill Editor using Cypress</strong></p><pre>cy.get(&#39;iframe#your-iframe-id&#39;).then($iframe =&gt; {<br>  const quill = $iframe.contents().find(&#39;.ql-editor&#39;);<br>  <br>  // Click the Quill editor to focus on it<br>  cy.wrap(quill).click();<br><br>  // Upload an image<br>  cy.fixture(&#39;image.jpg&#39;).then(fileContent =&gt; {<br>    cy.get(&#39;input[type=&quot;file&quot;]&#39;).upload({ fileContent, fileName: &#39;image.jpg&#39;, mimeType: &#39;image/jpeg&#39; });<br>  });<br><br>  // Wait for the image to be uploaded (customize wait time as needed)<br>  cy.wait(1000);<br>});</pre><p><strong>Clear text in a Quill Text-Editor using Cypress</strong></p><pre> cy.get(elementSelector).should(&#39;be.visible&#39;).then(($quillContainer) =&gt; {<br>    // Attempt to find the Quill editor within the container<br>    const quillEditor = $quillContainer.find(&#39;.ql-editor&#39;)[0];<br><br>    if (quillEditor) {<br>      // Use Quill&#39;s API to clear content<br>      cy.wrap(quillEditor).clear();<br>    } else {<br>      // Handle the case when Quill editor is not found<br>      throw new Error(&#39;Quill editor not found within the selected element&#39;);<br>    }<br>  });</pre><p>It is different from automating a standard plain text box/editor due to the complexities involved in handling formatted text, images, and other rich media elements.</p><p><em>And if you like this article, give a clap and follow for more. Thank you! 😊</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7e3a2d2f2da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why API Automation is better than UI Automation?]]></title>
            <link>https://medium.com/@dilkushi.j/why-api-automation-is-better-than-ui-automation-758a1d90da29?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/758a1d90da29</guid>
            <category><![CDATA[api-testing]]></category>
            <category><![CDATA[ui-automation-testing]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-automation]]></category>
            <category><![CDATA[api-test-automation]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 12:09:59 GMT</pubDate>
            <atom:updated>2023-10-01T15:21:15.350Z</atom:updated>
            <content:encoded><![CDATA[<p>API automation is the process of automating interactions with Application Programming Interfaces (APIs) using scripts, tools, or software.</p><p>UI automation, or User Interface automation, refers to the process of using software or tools to simulate user interactions with a graphical user interface (GUI) of a software application or system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91IE20fELJw_NaEcki-wlg.png" /></figure><p>Here are some reasons why API automation is considered better than UI automation in certain scenarios:</p><ul><li><strong>Faster Execution:</strong></li></ul><p>API tests tend to run faster than UI tests because they don’t involve rendering web pages or interacting with the user interface. API requests and responses are typically lightweight, leading to quicker test execution.</p><ul><li><strong>Stability:</strong></li></ul><p>UI tests can be fragile and sensitive to changes in the user interface, making them prone to breakage when UI elements or layouts change. API tests are generally more stable because they focus on the underlying business logic and data flow.</p><ul><li><strong>Coverage:</strong></li></ul><p>API tests can provide comprehensive coverage of the application’s functionality, including edge cases and error scenarios. UI tests may not cover all possible user interactions or inputs.</p><ul><li><strong>Efficiency:</strong></li></ul><p>API tests can be more efficient for repetitive tasks like regression testing or load testing because they require fewer resources and can be run in parallel.</p><ul><li><strong>Data Validation:</strong></li></ul><p>API tests are well-suited for data validation because they can easily verify the correctness of data returned by the API. UI tests may require additional effort to extract and validate data displayed on the user interface.</p><ul><li><strong>Cross-Platform and Cross-Browser Compatibility:</strong></li></ul><p>API tests are not dependent on specific browsers or platforms, making them more suitable for testing the backend of applications that need to work across different environments.</p><ul><li><strong>Early Detection of Issues:</strong></li></ul><p>API tests can be integrated into the development pipeline to catch issues early in the development process, promoting a shift-left approach to testing.</p><ul><li><strong>Reduced Maintenance:</strong></li></ul><p>UI automation scripts often require frequent updates due to changes in the user interface. API tests tend to have lower maintenance overhead since they are less affected by UI changes.</p><ul><li><strong>Scalability:</strong></li></ul><p>API automation can easily scale to test multiple endpoints, versions, or services in a micro-services architecture.</p><ul><li><strong>Isolation:</strong></li></ul><p>API tests can be isolated from the user interface, allowing you to test specific functionalities or endpoints independently. This isolation simplifies debugging and makes it easier to identify the root cause of issues.</p><h4><em>Let’s illustrate the difference between API automation and UI automation using a simple scenario of testing a login functionality.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iDySsMZEgG6FHf7VngYYiw.jpeg" /></figure><p>I am using two popular frameworks; Postman for API automation &amp; Selenium for UI automation.</p><h4>API Automation Example (Using Postman)</h4><p><em>In this API automation example, we’re using Postman to send a POST request to a login API endpoint. We then assert that the HTTP status code is 200 and that the response contains a “success” attribute set to </em><em>true.</em></p><pre>// Postman test script for API automation<br>pm.test(&quot;Login API Test&quot;, function () {<br>    // Define the API endpoint and request parameters<br>    const url = &quot;https://api.example.com/login&quot;;<br>    const request = {<br>        method: &quot;POST&quot;,<br>        url: url,<br>        header: {<br>            &quot;Content-Type&quot;: &quot;application/json&quot;,<br>        },<br>        body: {<br>            mode: &quot;raw&quot;,<br>            raw: JSON.stringify({<br>                username: &quot;testuser&quot;,<br>                password: &quot;password123&quot;,<br>            }),<br>        },<br>    };<br><br>    // Send the API request<br>    const response = pm.sendRequest(request);<br><br>    // Perform assertions on the API response<br>    pm.expect(response.code).to.equal(200); // Check HTTP status code<br>    pm.expect(response.json().success).to.be.true; // Check a specific JSON attribute<br>});</pre><h4>UI Automation Example (Using Selenium and Python)</h4><p><em>In this UI automation example, we’re using Selenium (with Python) to automate interactions with a web-based login page. We locate elements on the page, enter login credentials, click the login button, then verify the presence of a welcome message to confirm successful login.</em></p><pre>from selenium import webdriver<br><br># Set up the Selenium WebDriver for a web browser (e.g., Chrome)<br>driver = webdriver.Chrome()<br><br># Open the login page<br>driver.get(&quot;https://www.example.com/login&quot;)<br><br># Locate the username and password input fields and the login button<br>username_input = driver.find_element_by_id(&quot;username&quot;)<br>password_input = driver.find_element_by_id(&quot;password&quot;)<br>login_button = driver.find_element_by_id(&quot;login-button&quot;)<br><br># Enter login credentials and submit the form<br>username_input.send_keys(&quot;testuser&quot;)<br>password_input.send_keys(&quot;password123&quot;)<br>login_button.click()<br><br># Perform assertions on the UI to verify successful login<br>welcome_message = driver.find_element_by_css_selector(&quot;.welcome-message&quot;)<br>assert &quot;Welcome, testuser!&quot; in welcome_message.text<br><br># Close the browser<br>driver.quit()</pre><p>As you can see, API automation focuses on making HTTP requests and validating API responses, while UI automation interacts with the user interface of a web application.</p><h3>Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hPUzlidJNP8crsg0CdaVbg.png" /></figure><p><em>If you like this article, please show your support clicking the clap button below and follow for more. Thank you! </em><strong>😊👍</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=758a1d90da29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essential Communication Skills for QAs When Working with Developers]]></title>
            <link>https://medium.com/@dilkushi.j/essential-communication-skills-for-qa-professionals-working-with-developers-d13fceb5d1e5?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d13fceb5d1e5</guid>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[qa-skills]]></category>
            <category><![CDATA[flexible-work]]></category>
            <category><![CDATA[qa-testers]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Sat, 13 May 2023 08:13:25 GMT</pubDate>
            <atom:updated>2023-11-07T09:45:44.562Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>In a world where IT industry is heading towards more remote &amp; hybrid work culture, having strong communication skills help you to thrive and excel in this evolving landscape in several ways.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfCr1Au4u-IwZ755a66YXg.png" /></figure><p>As Quality Assurance (QA) professionals, effective communication with developers is important to build strong relationships, work effectively within the team, and ensure that software is developed and tested to meet the desired quality standards. Let’s go through them.</p><h3>Appreciate the work of Developers</h3><p>Developers play a critical role in software development, and their hard work and expertise should be acknowledged and valued always by the QA’s before pointing out bugs and issues and even after they are successfully fixed. Appreciating the work of developers helps positive work environment and fostering collaboration between QAs and developers.</p><h3><strong>Clear and concise communication</strong></h3><p>QAs should be able to convey their ideas and requirements in a clear and comprehensive manner. They should avoid using technical jargon or complex language that could confuse the developers. Clear communication helps to ensure that everyone is on the same page and that expectations are aligned.</p><blockquote>When using “this is a bug or this doesn’t work correctly” these types of statements can sometimes lead to conflicts between QA and development teams. Developers may immediately respond with “No, it can’t be. It worked fine for me” or “This is not a bug its a feature.” To avoid conflicts, it is important to communicate defects in a way that is less offensive and more effective.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BY0yqZ4uHHLS0Ve6ozlXrw.png" /></figure><blockquote>For example, instead of saying “there is a bug or this is broken”, a more polite and less confrontational approach would be, to say “Hey, I tried to do this but it didn’t work out the way I expected. Could we take a look and see if I did something wrong?” or try to do a pair testing with them focusing on the actual result and explaining what was expected, developers would be more likely to take ownership of the issue.</blockquote><h3>Flexibility</h3><p>QAs should be flexible in their communication style. Different developers may prefer different modes of communication, such as instant messaging, a quick call or face-to-face meetings, or an email. QA professionals should be able to identify their team members personalities<strong> </strong>and adapt to their preferred communication style to meet the needs of individuals.</p><h3>Active listening</h3><p>We should listen actively to what the developers have to say. They should be open to feedback and willing to collaborate with developers to find solutions to problems. Active listening helps to build trust and fosters a collaborative work environment.</p><h3>Detail-oriented</h3><p>QAs should be able to identify potential issues and report them to developers in a clear, evidence based and structured way<strong>.</strong> Being detail-oriented helps to ensure that bugs are caught early and resolved quickly.</p><h3>Technical Proficiency</h3><p>QA professionals should have a good understanding of technical concepts and programming languages. This helps them to understand the technical challenges that developers face. Having technical knowledge also enables QAs to identify potential issues and provide suggestions for improvements needed, review the code and find bugs in early stages.</p><h3>Self-Representation &amp; Engagement</h3><p>Visual engagement or turning on the camera during remote meetings helps to build a stronger connection, enhance team collaboration, and promote a more inclusive and interactive meeting experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*CrA0RdHNBhB_ZEwbnyx2gA.jpeg" /></figure><p>It represent your professionalism, dedication to teamwork, enhances communication, and promotes collaboration while being mindful of your own body language and that of others.</p><h3>Problem-Solving and Critical Thinking</h3><p>QAs should be able to think critically and work with developers to troubleshoot issues and find solutions. This may involve discussing alternative approaches or workarounds to resolve problems efficiently. Should analyse facts objectively, think clearly and rationally and only form a decision or judgment when the situation demands it.</p><h3>Adaptability</h3><p>The software development process is dynamic, and changes often occur. We must be able to adapt and responsive to these changes, including updates to requirements, timelines, and technology. Effective communication can help manage these changes smoothly.</p><h3>Empathy</h3><p>Understanding that developers often work under tight deadlines and may face challenges in their coding tasks can help QAs to approach communication with empathy. Being mindful of the developer’s perspective can lead to more productive and constructive interactions.</p><h3>Be respectful and supportive</h3><p>QAs should be respectful and supportive when communicating with developers. Avoid criticising or blaming developers for issues that arise and instead focus on finding solutions and working together to improve the software as a team work.</p><h3>Negotiation and Compromise</h3><p>In cases where there are disagreements or conflicts over issues, QA professionals should be skilled in negotiation and compromise. Finding common ground and reaching mutually acceptable solutions is vital.</p><p><em>If you like this article, show your support by clicking the clap button below and follow for more. Thank you </em>! 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d13fceb5d1e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effective Ways To Manage Your Scrum Board]]></title>
            <link>https://medium.com/@dilkushi.j/effective-ways-to-manage-your-scrum-board-e5dfe51a9b90?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5dfe51a9b90</guid>
            <category><![CDATA[agile-scrum-methodology]]></category>
            <category><![CDATA[scrum-agile]]></category>
            <category><![CDATA[scrum-board]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile-scrum-board]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Thu, 27 Apr 2023 07:02:06 GMT</pubDate>
            <atom:updated>2023-04-28T12:29:18.384Z</atom:updated>
            <content:encoded><![CDATA[<p>Scrum board is a visual tool that helps scrum teams to manage their work. Managing a Scrum board is essential for the success of any Agile project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hxvEESXZrUMqwlPbL9MDw.jpeg" /></figure><p><em>Here are some effective ways to manage your Scrum board:</em></p><h3>▪️ Keep the scrum board simple</h3><p>A simple scrum board is easier to manage and understand. Keep the number of columns to a minimum and use clear, concise labels. Keep the columns and cards simple and easy to read. Avoid overcomplicating the board with too many categories, subcategories, or detailed information that can lead to confusion.</p><h3>▪️ Use visual aids/ color codings</h3><p>Color coding helps to identify the status of tasks at a glance.</p><ul><li>Use different colours for different stages of completion, such as “To Do,” “In Progress,” and “Done.”</li><li>Use labels to indicate priority, progress, or status of tasks.</li><li>Visual aids such as colours, icons, and images can help to quickly convey information and make the board more engaging.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DjUxRSTO3pofMjrxZC8rXw.png" /></figure><h3>▪️ Limit work in progress</h3><p>Limit the number of tasks that can be in progress at any given time. This helps to prevent overloading team members and ensures that tasks are completed in a timely manner.</p><h3>▪️ Prioritize tasks</h3><p>Arrange the columns by priority, with high-priority tickets at the top and medium and low-priority ones below, in order to prioritize stories, tasks, tests, and bugs. This approach assists the team in concentrating on the most critical tasks initially.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*MqSTO9fl_YNoEFw0Si3o8g.jpeg" /></figure><h3>▪️ Hold daily stand-up meeting</h3><p>Hold daily stand-up meetings to review the Scrum board, discuss progress, and identify any roadblocks. This helps to keep everyone on the same page and ensure that the project is moving forward smoothly.</p><h3>▪️ Regularly update the board</h3><p>Make sure to update the board, status of tasks on regular basis, ideally daily, to ensure that everyone on the team is aware of the current state of tasks and progress. This helps the team to stay on top of the progress, identify any roadblocks, misunderstandings or confusion about what is being worked on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1iB6l7fMTwXzDjxMG0nYvA.jpeg" /></figure><h3>▪️ Review and refine</h3><p>Regularly review and refine the Scrum board to ensure that it is meeting the needs of the team. Make changes as needed to improve its effectiveness.</p><h3>▪️ Involve the whole team</h3><p>Ensure that the whole team is involved in managing the Scrum board, not just the Scrum Master or the Product Owner. Encourage the team to actively participate in updating the board, moving cards, and adding comments, so that everyone is invested in the process and is aware of what needs to be done.</p><h3>▪️ Collaborative &amp; supportive working environment</h3><p>Team members should feel comfortable asking for help and support when needed. The team should provide opportunities for learning and development, offer constructive feedback, and create a safe space for experimentation and innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7i-6VY-1C9A2CRuhKh05Yw.png" /></figure><h3>▪️ Effective communication</h3><p>Effective communication is essential for the success of a Scrum team. Developers should actively engage in peer reviews, inform testers when their tasks are ready for testing or when bugs are fixed. Similarly, testers should notify developers when tickets are ready to release. This leads tickets to move faster through board and more deliveries in the sprint.</p><h3>▪️ Keep the backlog prioritized</h3><p>Prioritising the backlog is essential to ensure that the most important tasks are being addressed first. Make sure to review and re-prioritize the backlog regularly to ensure that the team is always working on the most important tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gvf7HlsoRyvEEqdWNkdJQ.png" /></figure><h3>▪️ Keep the board visible &amp; accessible</h3><p>Make sure that the Scrum board is always visible to the team. It can be helpful to have a physical board in the workspace, but if that’s not possible, use a digital tool that can be accessed by everyone.</p><h3>▪️ Use scrum metrics &amp; KPIs</h3><p>Use metrics such as velocity or burndown charts to measure the team’s progress and identify areas where improvements can be made. This can help to identify bottlenecks and areas where the team may need additional support or resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0nBtAUguEHxnHNslz7-3g.jpeg" /></figure><p>By following these tips, you can effectively manage your Scrum board and keep your team on track to deliver successful projects.</p><p>Overall, effective Scrum board management requires good communication, collaboration, and a willingness to adapt and improve the process over time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5dfe51a9b90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Usability Testing]]></title>
            <link>https://medium.com/@dilkushi.j/usability-testing-bd3f1ebd86d1?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd3f1ebd86d1</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[uat-testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Thu, 20 Apr 2023 06:42:45 GMT</pubDate>
            <atom:updated>2023-06-19T08:08:18.272Z</atom:updated>
            <content:encoded><![CDATA[<p>Usability testing is a process of evaluating a product or system by testing it with actual users to determine how easy or difficult for them to use. The goal of usability testing is to identify usability problems and to gather feedback from users to improve the overall user experience.</p><h3>Methods of Usability Testing</h3><p>Usability testing can broadly be classified into 3 domains:</p><ul><li><strong><em>Moderated vs Unmoderated</em></strong></li><li><strong><em>Remote vs in person</em></strong></li><li><strong><em>Explorative vs comparative</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lcf1tri1D9P32aS5EB5_xA.png" /></figure><p><em>A usability-testing session involves a participant and a facilitator who gives tasks to the participant and observes the participant’s behavior.</em></p><p><strong>Facilitator : </strong>Guides the participant through test process.</p><p><strong>Tasks:</strong> Realistic activities participants perform in real life in an application.</p><p><strong>Participant</strong>: Realistic users of the product or service.</p><p>As the participant performs these tasks, the facilitator observes the participant’s behavior and listens for feedback. The facilitator may also ask followup questions to elicit detail from the participant.</p><h3>Types of Usability Testing</h3><p><em>There are different types of usability testing, each with its own approach and focus. Below are few of them.</em></p><p><strong>Exploratory Testing:</strong> This type of testing is conducted in the early stages of product development to explore user needs, attitudes, and behaviors. It is generally conducted using methods such as interviews, surveys, or user observations.</p><p><strong>Accessibility Testing: </strong>Accessibility testing is the process of evaluating a website, software, or application to ensure that it is accessible to people with disabilities, such as vision impairment, hearing disabilities, and other physical or cognitive conditions to create a better user experience for everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*OjawmRM0cTV_JmO46jrdWw.jpeg" /></figure><p><strong>A/B Testing:</strong> This involves comparing two or more versions of a software product or website to see which one performs better. Users are randomly assigned to different versions and their interactions with the software or website are tracked and analyzed to determine which version is more effective.</p><p><strong>Card sorting: </strong>This involves having users organize content or features of a software product or website into categories. This can help to identify how users think about and navigate through the product or website.</p><p><strong>Tree testing:</strong> This involves having users navigate through a site map or hierarchy of a website to find specific information or features. This can help to identify issues with the information architecture of the website.</p><p><strong>Comparative Testing:</strong> This type of testing is used to compare different versions of a product, or to compare a product with a competitor’s product. It helps to identify which version or product is more user-friendly and why.</p><h3>How to Conduct Successful Usability Testing ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*2akPiXeHS9OXglIIv6eAuA.png" /></figure><ul><li>Define Test Objectives: Determine what aspects of the product you want to evaluate and what specific goals you aim to achieve through the testing process.</li><li>Identify the target audience</li><li>Create testing scenarios and tasks</li><li>Recruit Participants: Recruit participants who match the identified user profiles.</li><li>Prepare the test materials: Select the appropriate tools and equipment to record the testing session. This may include cameras, screen recording software, and note-taking tools. Ensure that the equipment is set up properly before beginning the testing.</li><li>Conduct the testing session: Conduct the time boxed, testing sessions in a controlled environment with the participants. Observe the participant as they perform the scenarios and tasks, and take notes.</li><li>Collect feedback and improvements</li><li>Analyse the data &amp; report results</li><li>Make Design Improvements &amp; repeat testing</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*K2cZCPmEfO0JdtsG5_1SWA.png" /></figure><h3><strong>Test Artefacts and </strong>Deliverables <strong>in Usability Testing</strong></h3><p>Usability testing needs test artefacts to plan and design testing and delivers a variety of deliverables that can help improve the overall user experience of a software application.</p><p>Here are some common deliverables of usability testing:</p><ol><li><strong>Usability test plan:</strong></li></ol><p>A usability test plan outlines the objectives, scope, and methodology of the usability test. The plan includes details such as the target user group, testing environment, and testing tools.</p><p><strong>2. Test charters:</strong></p><p>A test charter provides the test conditions to cover during a time-boxed testing session. In exploratory testing, test design and test execution occur at the same time, guided by a prepared test charter.</p><p><strong>3. User manuals:</strong></p><p>A user manual is a document that provides instructions or information on how to operate or use a product, system, or service. User manuals typically include details on the features, functions, and operation of the product, as well as safety instructions, troubleshooting tips, and maintenance advice.</p><p><strong>4. Test scenarios and tasks:</strong></p><p>Usability testing involves defining scenarios and tasks that users will perform during testing. The scenarios and tasks are designed to test specific aspects of the software application and provide feedback on the user experience.</p><p><strong>5. Test results:</strong></p><p>Usability testing produces test results that document the issues and feedback identified during testing. The results may include written reports, recordings of user testing sessions, and other data that can be used to identify areas for improvement.</p><p><strong>6. Recommendations &amp; feedback for improvement:</strong></p><p>Based on the test results, usability testing may provide recommendations for improving the user experience of the software application. Recommendations may include changes to the design, layout, or functionality of the application.</p><p><strong>7. Usability metrics:</strong></p><p>Usability testing may use metrics such as task completion rates, time on task, and error rates to quantify the effectiveness and efficiency of the software application. These metrics can provide valuable insights into the user experience and help identify areas for improvement.</p><h4><strong><em>Is Usability Testing and User Acceptance Testing are same?</em></strong></h4><p><strong>While both usability testing and user acceptance testing involve testing a product with end-users, their goals and timing are different.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4WpxP51BADNEDBI1Eyr6BQ.jpeg" /></figure><p><strong>Usability testing</strong> is focused on evaluating the ease of use, learnability, and overall user experience of a product by observing users as they interact with it. Usability testing is typically conducted during the product development process to identify and address usability issues before the product is released to the public.</p><p><strong>User Acceptance Testing (UAT),</strong> on the other hand<strong> </strong>is a type of testing in which end-users test a product to determine whether it meets their requirements and is ready for release. UAT is typically conducted towards the end of the product development process, and its purpose is to ensure that the product is fit for purpose and meets the needs of its intended users.</p><blockquote><strong><em>Usability testing is focused on identifying and addressing usability issues, while UAT is focused on determining whether the product meets the user’s requirements and is ready for release.</em></strong></blockquote><p><em>If you like this article, please show your support clicking the clap button below and follow for more. Thank you! </em><strong>😊👍</strong></p><p><em>Check these insightful articles for further studies on usability testing:</em></p><ul><li><a href="https://www.globalapptesting.com/usability-testing">Usability testing - The Complete Guide</a></li><li><a href="https://usabilitygeek.com/remote-usability-testing-best-practices/">Remote Usability Testing - Best Practices - Usability Geek</a></li><li><a href="https://uxaudit.io/blog/Key-differences-between-usability-testing-and-user-testing/">4 Key differences between Usability Testing and User Testing - UXaudit.io</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd3f1ebd86d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aqua Cloud: The Future of QA Management, Powered by AI]]></title>
            <link>https://medium.com/@dilkushi.j/aqua-alm-the-future-of-qa-management-powered-by-ai-4700c60ec980?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4700c60ec980</guid>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Fri, 14 Apr 2023 00:20:06 GMT</pubDate>
            <atom:updated>2023-04-19T08:54:44.097Z</atom:updated>
            <content:encoded><![CDATA[<p>AI has become the future of the IT industry, while many people eagerly anticipating the opportunity to delegate their workload to these innovative tools. From data analysis to customer service, AI-powered tools are transforming the way. With that comes to the topic;</p><h4>Aqua-Cloud AI which is a powerful tool and innovative solution for QA management. <a href="https://aqua-cloud.io/">https://aqua-cloud.io/</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4xXif8E4TrN5z8o4gEYu-Q.png" /></figure><p><strong>What is Aqua-Cloud AI ?</strong></p><p>AQUA stands for Agile Quality Assurance.</p><p>It is an AI-powered solution for QA management with focus on saving time for testers, developers and their managers. It offers both Cloud and On-Premise deployment for your projects. It gives complete AI assistant which generates entire test case from a requirement.</p><p>But it is not just only Test Management Tool. Where else can we use it ?</p><ul><li><strong>Application Lifecycle Management Tool (ALM)</strong></li><li><strong>Requirements Management Tool</strong></li><li><strong>Application Testing</strong></li><li><strong>Web Testing</strong></li><li><strong>Test Case Management Tool</strong></li><li><strong>Automation Management Tool</strong></li><li><strong>User Acceptance Testing</strong></li><li><strong>Testing Tool for Jira</strong></li><li><strong>Bug Tracking &amp; Reporting</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHYjmJ2_0_LOWZkZucLixQ.jpeg" /></figure><p><strong>◼</strong>Can run projects of any complexity and any stage.</p><p><strong>◼</strong>Growing community with comprehensive documents and resources available.</p><p><strong>◼ ️</strong>Support agility: The entire team works together agile — in one application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J7-uWvg72bTBAH4fWTLaaw.png" /></figure><p><strong>◼ ️</strong>Supports multiple team sizes &amp; business groups (enterprise, midsize and small)</p><p><strong>◼ ️</strong>Not limited to IT industry and can be used in many other industries;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4R5ChmX3ZgmyGCPTn43MCg.png" /></figure><p><strong>◼ ️</strong>Easy migration process which is not expensive.</p><p><strong>◼ ️</strong>Availability of test report templates. (Test artefacts &amp; deliverables)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfaDPDJ4706uLZJxtldufg.png" /></figure><p><strong>◼ ️</strong>Create and generate custom reports, dashboards through data visualisation.</p><p><strong>◼ ️</strong>Can be integrated with external tools and plugins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UfonO1pZ4bBBDIaU3wScnw.png" /></figure><p><strong>◼ ️</strong>The application is fully localised and available in both English and German.</p><p><strong>◼ ️</strong>30 days free trial available.</p><h3>QA Test Management with AQUA</h3><p>Quality assurance is not just testing. It includes all the phases in software testing life cycle. AQUA is an Application Management Tool that supports all testing phases in STLC from requirement gathering to test design, test execution, test results reporting, bug tracking and defect reporting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZEQ5fuaQx6veLb8V5xPpw.jpeg" /></figure><blockquote>Generating Test cases with Aqua AI <em>🔍</em></blockquote><p><em>I am going to use Aqua AI to generate test cases for a given requirement and check its ability to design test cases as an effective test management tool.</em></p><p><strong>Steps:</strong></p><p><strong>1/ Go to ‘Navigation’ tab, select a project and click create a new requirement.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vafYQvgtzV3b8lL0AfF6mA.png" /></figure><p><strong>2/ Give a requirement name and add details and enter a descriptive description with AC as follows. Then save it.</strong></p><p><em>As a librarian, I want to be able to enter and manage the library’s collection of books, so that I can keep track of which books are available, who has borrowed them, and when they are due to be returned.</em></p><p><strong>Acceptance Criteria</strong></p><p><em>1. Add new books to the library’s collection:</em></p><ul><li>The book information (title, author, publication date, ISBN, etc.) must be accurately entered into the system.</li><li>The book must be searchable and visible in the library’s catalog.</li><li>The system should prevent duplicate entries for books with the same ISBN.</li></ul><p><em>2. Provide search functionality:</em></p><ul><li>The system should provide a reliable and user-friendly search function that allows patrons to search for books by title, author, ISBN.</li><li>The search results should be accurate, relevant, and up-to-date.</li></ul><p><em>3. Maintain a record of borrowed books:</em></p><ul><li>The system should accurately record the patron who borrowed the book and the date the book was checked out.</li><li>The system should automatically calculate and display the due date for each book.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sbz5EgupxT9OUXo5R2OF_Q.png" /></figure><p><strong>3/ Now click the ‘Test It’ button in the top</strong></p><p><em>First Aqua will automatically create a blank test case.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mu-rI8wTOUphvMxwcF1dJw.png" /></figure><p><strong>4/ Navigate to ‘Steps’ tab and click on ‘Copilot’ button.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ilq6TVReB7daiAEKS-g8RA.png" /></figure><p><strong>5/ Wait for few seconds to generate the results.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dp0xEZuPJx_de_56hPn9Hw.png" /></figure><p><strong>7/ Aqua AI has generated a comprehensive test case upon requirement.</strong></p><p>A very detailed test cases with clear steps have been generated. ✔️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrPhCQRyJ4OQWCvL5LrjFQ.png" /></figure><p><strong>8/ Now click the ‘Regenerate’ button and see results again.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HkmwIA62y_lQWPwNNArx4w.png" /></figure><p><strong>9/ Click ‘Apply’ Button and you can review the test cases as below.</strong></p><p>Test cases consists of instructions and expected results. Support both manual and automated tests. Test data and files can also be attached.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCME4yzoPjW59zDvDmoKoQ.png" /></figure><p>10/ Click <strong>‘Save’ </strong>button.</p><h3>My Experience of using Aqua Cloud AI- as a QA Engineer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*INwMj_7aNblj4xgN7Qi5VQ.jpeg" /></figure><p><strong>‘The performance of Aqua AI in generating test cases from requirements, exceeded my expectations.’ ☑️</strong></p><p>▪️ The inclusion of such a tool in a project has the potential to significantly reduce the workload of QA professionals, allowing them to allocate more time towards other critical testing tasks in the project.</p><p>▪️ <strong>The user interfaces are very intuitive and accessible, making them easy for first-time users to navigate.</strong> Numerous features have been implemented to enable the entry and maintenance of records for all aspects of the project covering detailed tests.</p><p>▪️ In addition to the results generated by AI, <strong>the presence of fields for manual input is an advantageous feature.</strong> This allows testers to manually enter details that may have been missed by the AI, ensuring comprehensive coverage of all possible scenarios.</p><p>▪️ The availability of the option to <strong>regenerate tests if the initial results are unsatisfactory</strong> is another valuable feature. By allowing tests to be regenerated, testers can easily modify and adjust their testing approach as needed to ensure highest level of quality and accuracy.</p><p>▪️ By generating a larger number of test cases through an AI, than a human could feasibly help identify potential bugs or issues that may have otherwise gone unnoticed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_FW3yUPDbkrM3wNdAFBNlw.jpeg" /></figure><blockquote>“The incorporation of Aqua AI in software testing represents a promising trend that has the potential to revolutionise the way QA professionals approach testing in the future.”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4700c60ec980" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future of Web Automation]]></title>
            <link>https://medium.com/@dilkushi.j/future-of-web-automation-bc54fe354968?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc54fe354968</guid>
            <category><![CDATA[web-automation-testing]]></category>
            <category><![CDATA[web-automation]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[future-of-testing]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Tue, 21 Mar 2023 17:33:38 GMT</pubDate>
            <atom:updated>2023-03-21T17:33:38.160Z</atom:updated>
            <content:encoded><![CDATA[<p>The future of web automation is very promising as companies are increasingly adopting digital transformation strategies by now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QNXpBKc-A6pwIFYrNlEYcA.jpeg" /></figure><p>Here are some key trends that are shaping the future of web automation:</p><ol><li><strong>Artificial Intelligence (AI)</strong></li></ol><p>One of the key trends in web automation is the use of Artificial Intelligence (AI) and Machine Learning (ML) to create more intelligent and sophisticated automation systems. These systems can learn from data and adapt to changing circumstances, making them more effective and efficient over time.</p><p><strong>2. DevOps</strong></p><p>DevOps is a set of practices and tools that aim to automate the software delivery process, from code development to deployment and maintenance. DevOps emphasizes collaboration between development and operations teams, and automation plays a critical role in achieving this collaboration.</p><p><strong>3. Low-code automation</strong></p><p>Low-code automation platforms are becoming more popular, allowing businesses to create customized automation solutions without the need for extensive programming expertise. These platforms enable organizations to build, test, and deploy automation solutions faster and more efficiently.</p><p><strong>4. Process automation</strong></p><p>Process automation is becoming more sophisticated, with businesses looking to automate more complex workflows and processes.</p><ul><li>Robotic Process Automation (RPA)</li><li>Business Process Automation (BPA)</li></ul><p>becoming more prevalent, allowing organizations to automate a wide range of tasks and processes like data entry, customer service, and finance.</p><p><strong>5. Integration with other technologies:</strong></p><p>Automation is increasingly being integrated with other emerging technologies such as</p><ul><li>Blockchain</li><li>Internet of Things (IoT)</li><li>Cloud Computing</li></ul><p>This integration enables businesses to create more comprehensive automation solutions that can automate complex workflows and processes, and ensure that data is secure and tamper-proof.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc54fe354968" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Cypress Upgrade: Version 12]]></title>
            <link>https://medium.com/@dilkushi.j/new-cypress-upgrade-version-12-16006e76bbb1?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/16006e76bbb1</guid>
            <category><![CDATA[cypress-testing]]></category>
            <category><![CDATA[cypressio]]></category>
            <category><![CDATA[testing-framework]]></category>
            <category><![CDATA[cypress-framework]]></category>
            <category><![CDATA[cypress]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Thu, 16 Mar 2023 20:45:08 GMT</pubDate>
            <atom:updated>2023-03-16T20:47:11.348Z</atom:updated>
            <content:encoded><![CDATA[<p>Cypress announced the new version V12 at end of the last year and it came up with some great features. In this blog we will discuss about the new features of the Cypress Version 12 and steps to upgrade it in your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r61WRIumleFXAmkQBTMaqg.jpeg" /></figure><h3>New Features</h3><h4>▪️ Test Isolation</h4><p>Cypress e<strong>nd-to-end tests are now set test isolation to true by default</strong>, which means that we reset the cookies, storage, and the page state before each test. Any tests that relied on the browser to be at a certain state (like from a previous cy. visit() ) will not work with the new test isolation behavior.</p><h4>▪️ Supports Node.js 14+</h4><p>Cypress comes bundled with its own <a href="https://github.com/cypress-io/cypress/blob/develop/.node-version">Node.js version</a>. When installing the cypress npm package uses the Node.js version installed on our system. The minimum Node.js version supported now to install Cypress is Node.js 14+.</p><h4>▪️ Behavior Changes in Alias</h4><p>Cypress always re-queries aliases when they are referenced. This can result in certain tests that used to pass could start to fail. If we want to alias a static value, cypress introduced the type option for <a href="https://docs.cypress.io/api/commands/as">.as()</a> to opt into the old behavior.</p><h4>▪️ New Query Commands</h4><p>A query is a small and fast command for getting data from the window or DOM. This is important as Cypress can retry chains of queries, keeping the yielded subject up-to-date as a page re-renders. With the introduction of query commands, some commands have been re-categorized and can no longer be overwritten with <a href="https://docs.cypress.io/api/cypress-api/custom-commands#Overwrite-Existing-Commands">Cypress.Commands.overwrite()</a>:</p><h4>▪️ Fix for detached DOM errors</h4><p>The upcoming Cypress 12 release includes a fix for the long-standing and frustrating “Detached DOM” error. The DOM resolution logic has been improved to query new elements that may have replaced older ones due to DOM updates, leading to more reliable and stable tests.</p><h4>▪️ Cypress API Changes</h4><p>Cypress has undergone some API changes where commonly used APIs have been replaced with commands.</p><blockquote><em>The </em><em>Cypress.Cookies.defaults and </em><em>Cypress.Cookies.preserveOnce APIs have been removed, and the </em><em>cy.session() command is recommended for preserving cookies, local and session storage between tests.</em></blockquote><blockquote><em>The </em><em>cy.server(), </em><em>cy.route() commands, and the </em><em>Cypress.Server.defaults API have been removed. The </em><em>cy.intercept() command should be used instead.</em></blockquote><blockquote><em>The </em><em>.invoke() command will throw an error if a function returns a promise, and users should now use </em><em>.then() instead.</em></blockquote><blockquote><em>The </em><em>.should() assertion will now throw an error if Cypress commands are used inside the callback, and users should now use </em><em>.then() instead.</em></blockquote><blockquote><em>The </em><em>.within() command will now throw an error if multiple elements are passed as the subject.</em></blockquote><h3>Migration from Version 10 to Version 12</h3><ol><li>You can navigate to package-lock.json file in your project to check your Cypress version. Currently I’m working in Cypress 10.11.0</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2vbeLwWI7j0chR_lUkDkg.png" /></figure><p>2. First switch to master and create a branch.</p><p>3. Now open the cypress runner. <em>npm cypress open</em>And click on the Version upgrade button on the right top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VfX65ESh39dlSfJVZR01bA.png" /></figure><p>4. You can see which version you are using currently. Now click the blue button ‘upgrade to 12.8.1’. It will appear the latest available version there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5txoQpFqk9Kq43nl7oT7Sw.png" /></figure><p>5. Copy the command <em>npm install -D cypress@12.8.1</em> as shown here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJqupFx3z-VRGeQSX6ve3w.png" /></figure><p>6. And paste it in the terminal and click enter to run the command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9anzEiyaLcIJ73OmdW9AA.png" /></figure><p>7. You can see the package-lock.json and package.json has been updated. Check the dev Dependencies in package-lock.json to see cypress has upgraded to new version. You can see here ‘cypress’: ‘12.8.1’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1dvXRzRdVKl4CIcZfhlpNw.png" /></figure><p>8. If the branch has no conflicts, commit the changes, and merge the PR.</p><blockquote><em>Thank you and don’t forget to follow for more ! 👍</em></blockquote><blockquote><em>For Further References :</em></blockquote><ul><li><a href="https://docs.cypress.io/guides/references/migration-guide">Migration Guide | Cypress Documentation</a></li><li><a href="https://www.cypress.io/blog/2022/12/06/announcing-cypress-12/">Announcing Cypress 12</a></li><li><a href="https://glebbahmutov.com/blog/upgrade-cypress-v9-to-v12/">Upgrade Cypress From Version 9 to Version 12</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16006e76bbb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can Chat-GPT replaces a Software Tester ?]]></title>
            <link>https://medium.com/@dilkushi.j/can-chat-gpt-replaces-a-software-tester-9ec2fdf60152?source=rss-d7321c2f3d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ec2fdf60152</guid>
            <category><![CDATA[qa-trends]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[software-tester]]></category>
            <dc:creator><![CDATA[Dilkushi Jayaweera]]></dc:creator>
            <pubDate>Sun, 05 Mar 2023 00:03:44 GMT</pubDate>
            <atom:updated>2023-03-13T23:17:06.932Z</atom:updated>
            <content:encoded><![CDATA[<h3>Can Chat-GPT Replaces a Software Tester ?</h3><blockquote>“As the modern AI trend, ChatGPT is at its peak of success and attention, it is time to examine its influence in field of software testing and for testers”</blockquote><p>Chat-GPT has the ability to improve the efficiency and effectiveness of software testing through testing and automation, it is unlikely that most companies willing to replace human testers with AI systems to an extent.</p><p><strong>But can Chat-GPT replaces unique skills and values of a software tester ?</strong> Let’s discuss in this blog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RP9rYYsTB_SzAiv_2dSBdg.png" /></figure><h3>Limitations of Chat GPT in Replacing a QA Tester</h3><p>First let’s explore, why Chat-GPT cannot challenge a software tester.</p><p><strong>◼️ Requirements Analysis</strong></p><p>A software tester has the ability to understand the requirements of a software project and verify if the product meets those requirements. ChatGPT, on the other hand, lacks the ability to understand the requirements, making it difficult for it to test a software project effectively.</p><p><strong>◼️ Experience Matters</strong></p><p>A software tester has a deep understanding of software development processes and testing methodologies, and is able to use their experience and expertise to identify potential risks, issues and bugs from their practice over the years, that might not be apparent to an AI language model.</p><p><strong>◼️ Testing is Multi-Tasking</strong></p><p>Software testing involves a wide range of tasks beyond just generating &amp; executing tests and finding bugs. This includes multi-tasking such as developing test plans &amp; strategies, performing manual &amp; automation testing, working with developers to resolve issues &amp; bugs, suggesting improvements and acquiring quality of the product which a huge responsibility an AI cannot perform.</p><p><strong>◼️ Logical Thinking</strong></p><p>QA Engineers possess domain knowledge, critical thinking and analytical skills and creativity that are essential for solving complex problems and identifying edge cases that may not be covered by automated testing. It cannot replace the human intuition and judgment that are necessary for ensuring the quality and reliability of software applications.</p><p><strong>◼️ Handling Complex Test Scripts</strong></p><p>There are certain complex test scenarios that Chat-GPT may not be able to handle effectively. It may struggle to generate test cases that involve a series of interconnected steps or complex workflows that require specific inputs and outputs which will be challenging for an AI model to handle.</p><p><strong>◼️ Accurate Decision-Making</strong></p><p>ChatGPT is a machine learning model that relies on algorithms to generate responses to user input. While it can learn from large datasets and generate responses with a high degree of accuracy, it still lacks the ability to understand the context of a problem, anticipate user needs, and perform exploratory testing and proper decision making according to the situation.</p><p><strong>◼️ Testing is a Team Work</strong></p><p>Testing is a team effort that requires collaboration and communication among all members of the project. Interacting with the business, stakeholders and gaining feedback is and modify changes to frequent requirements is actually a team work that single AI cannot perform alone.</p><h3>Experimenting Chat-GPT to Create a Test Scenario</h3><p>For future understanding let’s try out an experiment with Chat-GPT to create a test scenario &amp; compare the results how Chat-GPT and an actual human tester will handle it.</p><p>By comparing the performance, we can gain insights on effectiveness and limitations of Chat-GPT as an AI model contribution for software testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AXHjtRU4NHScFxhoDyY2A.jpeg" /></figure><p><strong>1)Steps: </strong>Let’s create login test scenario for given website using Chat-GPT 🔍</p><p>The prompt I’m using is <strong>“Write a test scenario for testing the login of </strong><a href="https://practicetestautomation.com/practice-test-login/"><strong>https://practicetestautomation.com/practice-test-login/</strong></a>”.</p><p>And the result is shown in the attached image below.👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a23HZpdYh-qeWR9XMk9CeA.png" /></figure><p><strong>2) Results:</strong> (<em>Note that the results may differ often with the inputs we use)</em></p><p><strong>The outcome is actually satisfying and it has written the test scenario in a well-organised and structured manner with expected steps covered. </strong>✅</p><p><strong>3) Comparison :</strong></p><p><strong>◼ ️Covers Only the Happy Path</strong></p><p>This scenario looks pretty basic which covers only the happy path. But if the same question is been asked from a software tester they will provide an answer, covering both positive &amp; negative scenarios along with edge cases.</p><p><strong>◼ ️Executes Only the Requested Task</strong></p><p>Chat-GPT will provide answers for the negative test scenarios if it’s been asked in the next round of course, but a software tester will provide an answer with a better test coverage at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0eUly149184rf5wBbTQuyQ.png" /></figure><p><strong>◼ ️Operates Within the Scope</strong></p><p>Above is the image of the login page given for testing. In step <br><em>5. Click on the “Login” button instead of the actual text displaying is ‘Submit’ button on the form.</em></p><p>But a manual software tester is less likely to encounter such mistakes.</p><p><strong>◼ ️Same Repetitive Results</strong></p><p>If the same question has been asked again it will provide results which are not quite different from the first result. But it will be focusing on login. But a software tester will often be more creative to go an extra mile.</p><p><strong>◼ Limited Knowledge</strong></p><p>Chat-GPT itself states ‘Limited knowledge of world and events after 2021’. under its limitations and here is one of the best examples I can provide;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pUVCeZ48iqMLL9dl4Ss-RA.png" /></figure><p><strong>◼ ️Not Thinking Outside the Box</strong></p><p>Software tester will be thinking outside the box and come up with scenarios and tests that checks the friendliness of the UI, logos and images which an AI will difficult to understand and provide results.</p><blockquote>The above data clearly provides insights, effectiveness and limitations of Chat-GPT challenging software tester and why it cannot replaces a software tester.</blockquote><h3>Final Thoughts</h3><p>While Chat GPT and other AI technologies can be used as part of manual and automated testing frameworks and enhance the capabilities of software testers in a good way, it cannot fully replace the technical skills, standard quality and expertise that skilled QA tester adds to a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N-4_LvIshf2I62uaNSFVFA.jpeg" /></figure><blockquote>“Therefore, software testing will continue to be an important role in software development, while AI technology continues to evolve &amp; transform the field.”</blockquote><p>So what do you think? Can Chat-GPT replace a unique skills and values of a software tester? I would love to hear your impressions and thoughts. Feel free to share you ideas and insights with me.</p><p>If you like this article don’t forget to give me a clap and follow for more.<br>See you in another blog. Thank you ! 🤗</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ec2fdf60152" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>