<?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 Gokcemusul on Medium]]></title>
        <description><![CDATA[Stories by Gokcemusul on Medium]]></description>
        <link>https://medium.com/@gokcemusul?source=rss-e9178517955b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*H5pOlWgMKe1kuw2-jG4p6Q.jpeg</url>
            <title>Stories by Gokcemusul on Medium</title>
            <link>https://medium.com/@gokcemusul?source=rss-e9178517955b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:56:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gokcemusul/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[From Selenium Side Projects to FinTech/High-Frequency Frameworks: A 3-Stage Evolution of an SDET]]></title>
            <link>https://medium.com/@gokcemusul/from-selenium-side-projects-to-fintech-high-frequency-frameworks-a-3-stage-evolution-of-an-sdet-15d191fe3d95?source=rss-e9178517955b------2</link>
            <guid isPermaLink="false">https://medium.com/p/15d191fe3d95</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[sdet]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[career-growth]]></category>
            <dc:creator><![CDATA[Gokcemusul]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 09:01:39 GMT</pubDate>
            <atom:updated>2026-01-07T09:01:39.192Z</atom:updated>
            <content:encoded><![CDATA[<p>Like many in our field, I started my automation journey with the classic “Hello World” of SDETs: writing a script to automate a basic Google search. Those side projects gave me confidence. But when I stepped into the real world of FinTech, I realized that <strong>knowing the syntax and engineering a framework are two completely different things.</strong></p><p>Here is the story of how I transitioned from running manual tests to architecting systems that handle thousands of daily checks in a high-frequency trading environment.</p><h3>Stage 1: The Real School—Debugging Over Coding</h3><p>My first real assignment wasn’t to write a shiny new test suite from scratch. It was to maintain the company’s existing in-house framework. At first, honestly, it felt intimidating. The codebase was massive, complex, and nothing like my simple side projects.</p><p>But looking back, this was my real school.</p><p>Instead of writing lines of code, I spent my days reading them. I dove deep into server logs, hunting down the root causes of failures. My most frequent adversaries were the infamous NullPointerException and IndexOutOfBoundsException.</p><p>Fixing these wasn’t just about patching a line; it was about understanding the data flow.</p><ul><li><em>Why was this list empty when the market opened?</em></li><li><em>Why did the array size mismatch the incoming order data?</em></li></ul><p>This phase taught me defensive coding, <strong>OOP principles</strong>, and the critical importance of data structures far better than any online course could. I learned that before you can build, you must understand how to repair.</p><h3>Stage 2: The Domain Deep Dive—Logic Over Syntax</h3><p>As I grew comfortable with the code, my role shifted from fixing bugs to implementing features. This was where the <strong>FinTech domain</strong> really kicked in.</p><p>In trading systems, adding a new “Order Type” isn’t just about adding a dropdown item on the UI. It starts deep in the backend. I learned to work backwards:</p><ol><li>First, implement the <strong>API definition</strong> for the new message type within the framework.</li><li>Then, understanding the business logic: If this order is rejected, exactly which error code should the system return?</li><li>Finally, writing the test cases to verify both success and failure scenarios.</li></ol><p>I wasn’t just checking if a button worked; I was validating <strong>financial protocols</strong>. I found myself refactoring the framework to better handle these complex logic flows, ensuring that our automation understood the difference between a “System Error” and a valid “Business Reject.”</p><p>This bridge between technical architecture and business logic is where I truly became an SDET.</p><h3>Stage 3: The Architect—Building from Scratch</h3><p>All those late-night debugging sessions and API implementations eventually paid off. When the company needed a new automation infrastructure for our Web Trader application, I didn’t just “write scripts”; I engineered a solution.</p><p>Leveraging the OOP principles and structural discipline I learned from the core legacy framework, and I built a new framework from the ground up. This time, I knew exactly how to handle data, how to structure the <strong>Page Object Model</strong>, and how to make the tests resilient against changes.</p><p>Today, between the core backend framework and the UI projects I maintain, we run over <strong>2,500 test cases daily on Docker containers.</strong></p><p>The transition from Manual QA to <strong>Lead SDET</strong> wasn’t about learning a specific tool like Playwright or Selenium. It was about shifting my mindset:</p><ul><li>From reporting bugs to <strong>understanding the code</strong> that caused them.</li><li>From black-box testing to <strong>white-box engineering</strong>.</li><li>From running tests to <strong>designing systems</strong>.</li></ul><h3>Final Thoughts</h3><p>If you are looking to make this transition, don’t just focus on the syntax of a language. Read code to understand the logic, debug fearlessly because exceptions are your best teachers, and know your domain deeply.</p><p>A good coder can write a loop, but a good SDET knows why that loop matters for the business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15d191fe3d95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QA Trends This Week: AI’s Role in Test Automation & Key Tool Updates]]></title>
            <link>https://medium.com/@gokcemusul/qa-trends-this-week-ais-role-in-test-automation-key-tool-updates-cc8df99733e3?source=rss-e9178517955b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc8df99733e3</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[ai-testing]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[testrail]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Gokcemusul]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 18:10:39 GMT</pubDate>
            <atom:updated>2025-08-04T18:10:39.930Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*32M_kWSMzDqggwyjjNSZIA.png" /></figure><p>Week of August 04, 2025, by Gökçem Usul</p><p>As AI continues to influence every corner of software development, QA is becoming one of its most dynamic playgrounds. Beyond the hype, there’s a clear trend: AI is no longer a futuristic promise; it’s shaping how we prioritize tests, predict risks, and manage quality pipelines in real-time.</p><p>This week’s highlights show how AI and TestOps are working together to redefine testing workflows.</p><h3>1. AI-Driven Test Coverage Estimation is Gaining Adoption</h3><p>Testim and Functionize are pushing new models that automatically analyze code changes and suggest which areas need more testing attention. These models don’t just look at lines of code but at user flows, historical defect data, and integration complexity.</p><p>This is moving QA teams closer to predictive quality engineering, where resources are focused on the areas most likely to break.</p><p>It’s not about AI writing all the tests. It’s about using AI to direct human effort smarter.</p><h3>2. Cypress 13.0 Release—Focus on Stability and DX</h3><p>Cypress has rolled out version 13.0 with several developer experience improvements, including enhanced flaky test detection and faster CI integrations. There’s also a big push towards making cross-browser testing more reliable.</p><p>While Playwright is expanding into component testing, Cypress is doubling down on reliability for complex E2E scenarios.</p><p><a href="https://docs.cypress.io/guides/references/changelog#13-0-0">View Cypress 13.0 Changelog</a></p><h3>3. TestOps Dashboards Are Becoming Decision-Making Tools</h3><p>TestRail and PractiTest have updated their dashboards to include traceability metrics, coverage heatmaps, and AI-generated risk zones. These dashboards are no longer just reports; they’re being used actively in release planning and go/no-go meetings.</p><p>This shift elevates QA’s role from status reporting to risk advising.</p><p>The better we communicate test data, the more influence we have over release quality.</p><h3>Final Thought</h3><p>Test automation is evolving fast, but staying effective isn’t about automating everything. It’s about knowing <strong>where</strong> and <strong>why</strong> we automate. AI and TestOps are tools, but strategy and clarity will always be our edge.</p><p>Thanks for reading<br> Gökçem Usul</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc8df99733e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QA Trends This Week: AI, Playwright, and TestOps Insights]]></title>
            <link>https://medium.com/@gokcemusul/qa-trends-this-week-ai-playwright-and-testops-insights-3184cd1dc352?source=rss-e9178517955b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3184cd1dc352</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Gokcemusul]]></dc:creator>
            <pubDate>Sun, 27 Jul 2025 18:13:09 GMT</pubDate>
            <atom:updated>2025-07-27T18:30:04.088Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*se8cVvOt58X5WSwfLQeUug.png" /></figure><p>Week of July 27, 2025<br> by Gökçem Usul</p><p>Test automation is no longer just about reducing manual effort or writing thousands of scripts. It’s evolving into something much more strategic. The focus is shifting toward smarter systems, data-informed decisions, and tighter collaboration with development and operations teams.</p><p>Here are three highlights from this week that reflect where the QA world is headed.</p><h3>1. AI-Powered Test Prioritization is Becoming More Practical</h3><p>With the help of large language models, some tools can now analyze commit history and highlight the most risky areas in the codebase. Based on that, they suggest which tests should be prioritized first during execution.</p><p>Products like Launchable and Testim are already exploring this model. It doesn’t replace human decision-making, but it definitely helps reduce noise and focus effort where it matters.</p><h3>2. Playwright 1.44 Brings Native Component Testing</h3><p>The latest Playwright release includes built-in support for component testing. This puts it in direct competition with Cypress, especially for React and other frontend-heavy applications.</p><p>The update also includes improvements in TypeScript support and locator stability. It’s clear that Playwright is trying to become a one-stop solution for full-stack test automation.</p><p><a href="https://playwright.dev/whats-new">View Release Notes</a></p><h3>3. TestOps Tools are Maturing Fast</h3><p>Tools like TestRail, PractiTest, and Zephyr are expanding beyond basic test case tracking. They now offer dashboards, traceability reports, quality metrics, and release gating features.</p><p>What used to be a supporting role is now becoming a strategic one. QA teams are gaining a stronger voice by making test data more visible and meaningful during release cycles.</p><h3>Final Thought</h3><p>Testing is no longer just a safety net. It’s part of the architecture. The more informed we are, the more value we bring.</p><p>Thanks for reading<br> Gökçem Usul</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3184cd1dc352" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Useful Linux Commands for Managing your Test and Development Environment]]></title>
            <link>https://medium.com/@gokcemusul/useful-linux-commands-for-managing-your-test-and-development-environment-7fcee93634ee?source=rss-e9178517955b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fcee93634ee</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <category><![CDATA[command-line]]></category>
            <dc:creator><![CDATA[Gokcemusul]]></dc:creator>
            <pubDate>Sat, 08 Oct 2022 14:38:41 GMT</pubDate>
            <atom:updated>2022-10-08T14:38:41.512Z</atom:updated>
            <content:encoded><![CDATA[<p>For more than 3 years apart, I have been working with Linux Environments. <br>For this purpose, in this article, I wanted to share the most common Linux command lines in my everyday life. <br>This article notably consists of directory management, and file management. In addition, I wrote some additional commands, since I use them in my daily life vastly.</p><h3>Directory Management</h3><p>The very beginning thing to manage your environments is directory commands.</p><h4>ls</h4><p>This command displays a list of content of the current directory. You can use this command with different parameters. These parameters help you to list the content you want.</p><p>For example,</p><blockquote>ls -a, the -a parameter shows all content of the directory including the hidden files. <br>ls -l, the -l parameter shows the list in a long list format.</blockquote><blockquote>ls -lt, -lt parameter shows the list by recently modified file at the top.</blockquote><blockquote>ls -r, -r parameter prints the list in reverse order.</blockquote><p>I generally use <em>ls -latr</em> command to show my working directory content. Thus, it shows all content including hidden files, with the last changed at the bottom.</p><pre>Syntax: ls -latr</pre><h4>pwd</h4><p>Print working directory. This command displays the content of the current working directory.</p><pre>Syntax: pwd</pre><h4>mkdir</h4><p>This command creates a new directory under any directory.</p><pre>Syntax: mkdir &lt;directory_name&gt;</pre><h4>cd</h4><p>This command changes the current directory.</p><pre>Syntax: cd &lt;directory_name&gt;</pre><p>If you want to change your directory to home directly, it is enough to type:</p><pre>Syntax: cd ~ or cd</pre><p>in any directory. This command changes your directory to the home directory in your environment.</p><h4>rmdir</h4><p>This command removes your directory. This command only works for empty directories. You can also remove multiple empty directories with this command.</p><pre>Syntax: rm &lt;directory_name&gt;</pre><p>Be careful with this command. Because if you remove permanently files, directories, etc. in your Linux environment. The only way to recover them is from backup.</p><h4>rm</h4><p>This command also uses for removing files, directories, etc.</p><blockquote>rm -d removes the empty directories.</blockquote><blockquote>rm -r, -r(recursive) removes non-empty directories with all their contents.</blockquote><blockquote>rm -f, -f(force), forces to remove all files and directories.</blockquote><h3>File Management</h3><h4>cp</h4><p>The copy command uses to copy files or directories. Also, it uses to copy files and directories to other directories.</p><pre>Syntax: cp &lt;file_name&gt; &lt;new_file_name&gt;</pre><pre>Syntax: cp &lt;file_name&gt; &lt;directory_name&gt;</pre><h4>mv</h4><p>The mv command uses to change the file or directory name. Also, change files or directories from one location to other.</p><pre>Syntax: mv &lt;file_name&gt; &lt;directory_path&gt;<br>Syntax: mv &lt;file_name&gt; &lt;new_file_name&gt;</pre><blockquote>The difference between the cp and mv commands to change file name is. Changing the file name with the cp command, the old file remains. However, by changing your file name with the mv command, the old file will no longer exist.</blockquote><h4>scp</h4><p>The scp (secure copy) command copies files and directories between two locations.</p><p>It is so useful command notably if you work with multi-node environments and working with more than one Linux environment. Instead of downloading files and directory contents in your local environment and then to your target environment manually, this command helps you to transfer your contents directly to your target.</p><pre>Syntax: scp &lt;file_name&gt; &lt;user_name&gt;@&lt;target_hostname or target_IP&gt;:&lt;target_directory_name&gt;</pre><pre>scp example gokcem@tagethost:/tmp</pre><pre>scp /tmp/example gokcem@targethost:/tmp</pre><h4>touch</h4><p>This command creates empty files. You can also create multiple files with this command.</p><pre>Syntax: touch &lt;file_name&gt;</pre><pre>Syntax: touch &lt;file_name1&gt; &lt;file_name2&gt;</pre><h4>cat</h4><p>This command shows you the content of the files.</p><pre>Syntx: cat &lt;file_name&gt; </pre><h4>less</h4><p>This command is especially useful for large content files. Because it shows the contents of a text one screen at a time. For example, application log files, since application log files have large content, you can use this command to observe the content.</p><pre>Syntax: less &lt;file_name&gt;</pre><pre>Shortcut: Cltrl + F </pre><blockquote>If you observe file with less command, you can directly press Ctrl + F and see end lines of files automatically.</blockquote><h4>Input/ Output Redirections</h4><p>Redirection operators “&gt; and &gt;&gt;” generally uses for saving the output to a file instead of showing the output on a screen.</p><blockquote>&gt; redirects the command output to a file.</blockquote><blockquote>&gt;&gt; redirects the command output at the ends of existing content.</blockquote><blockquote>Be careful, with the &gt; operator, if you are redirecting your command output to an existing file, the previous content will be removed completely. Since it redirects as new content and overrides existing one.</blockquote><pre>Syntax: command output &gt; new_file</pre><pre>Syntax: command output &gt;&gt; new_file</pre><h3>Additional Commands</h3><h4>cd -</h4><p>This command changes your directory to the last working directory. This is useful because instead of writing your last working directory path manually, write only cd -.</p><pre>Syntax: cd -</pre><h4>ctrl + R</h4><p>This command searches backward your commands historically. It is very useful to type your repetitive commands.</p><pre>Syntax: Ctrl + R and type first letter or letters of command that you issued to find</pre><p>Hope you find this content resourceful. I will continue to share new content soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fcee93634ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Test Automation Framework from Scratch with Selenium, Java, and TestNG Part — 1]]></title>
            <link>https://medium.com/@gokcemusul/building-a-test-automation-framework-from-scratch-with-selenium-java-and-testng-part-1-2d75378c09b3?source=rss-e9178517955b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d75378c09b3</guid>
            <category><![CDATA[testng-framework]]></category>
            <category><![CDATA[selenium-testing]]></category>
            <category><![CDATA[selenium-test-automation]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[selenium-webdriver]]></category>
            <dc:creator><![CDATA[Gokcemusul]]></dc:creator>
            <pubDate>Sun, 06 Mar 2022 20:17:40 GMT</pubDate>
            <atom:updated>2022-03-06T20:54:44.005Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a Test Automation Framework from Scratch with Selenium, Java, and TestNG Part — 1</h3><p><strong><em>Brief Introduction to Selenium WebDriver</em></strong></p><p>Selenium is a widely used, and open-source suite of software, and consists of WebDriver, IDE, RC, and Grid.</p><p>WebDriver drives a browser natively, as the user would do. Also, it performs either locally or on a remote machine using the Selenium server.</p><p>This helps us to automate the tasks performed manually on browsers. In addition, it can handle automating complex tasks like selecting an option from dropdowns, selecting checkboxes, etc.</p><p>Moreover, it supports different languages which also includes Java, and in this article, we will be building a test automation framework by Selenium WebDriver with Java.</p><blockquote>For Implementing the framework, the “https://www.saucedemo.com/&quot; site is used.</blockquote><blockquote>The repository of the framework <a href="https://github.com/Gokcemu/uiautomation-framewok">https://github.com/Gokcemu/uiautomation-framewok</a></blockquote><p><strong><em>Implementing a Page Object Model by Building an Automation Framework</em></strong></p><p>Page Object Model is a commonly used design pattern in test automation that creates an Object Repository for web UI elements. By implementing this model, every page has a corresponding page class. This is given as an advantage of reducing code duplication and improving test maintenance.</p><p>In addition, an automation framework project structure is based on two layers which are automation and test layer.</p><p>The automation layer would include framework side handling WebElements and performing operations with elements like clicking, hovering, selecting.</p><p>In the test layer, a separate class can be created for tests related to tasks.</p><p><strong><em>WebElements and WebElement Commands</em></strong></p><p>WebElement is anything presented on Webpage, it represents an HTML element, and it can be of any type including checkboxes, dropdowns, buttons, etc.</p><p>All interactions within a WebElement on-page will be performed through WebElements Interface. There exists an entirely different set of commands for performing different tasks on the Interface.</p><p>There is also a document that represents the all methods that we can use to interact with elements.</p><p><a href="https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/WebElement.html">WebElement</a></p><p>Commands are simply methods written in Java Language since our framework building with Java.</p><p>Before performing operations on WebElements by helping WebElement commands, we should locate the elements. In this framework, for a login page, for example, there exists a Username, Password, Login Button, and Error Message Container elements. Concerning Page Object Model, we created a class for the login page, and in this class, identified locators for each element and used the commands for performing tasks.</p><pre>public class LoginPage {<br><br>    private WebDriver driver;<br>    private By usernameField = By.<em>xpath</em>(&quot;//input[@placeholder=&#39;Username&#39;]&quot;);<br>    private By passwordField = By.<em>xpath</em>(&quot;//input[@placeholder=&#39;Password&#39;]&quot;);<br>    private By loginButton   = By.<em>xpath</em>(&quot;//input[@name=&#39;login-button&#39;]&quot;);<br>    private By errorAlert    = By.<em>xpath</em>(&quot;//div[@class=&#39;error-message-container error&#39;]&quot;);<br><br><br>    public LoginPage(WebDriver driver){<br><br>        this.driver = driver;<br>    }<br><br>    public String getErrorAlert(){<br><br>        return driver.findElement(errorAlert).getText();<br>    }<br><br>    public void setUsernameField(String username){<br><br>        driver.findElement(usernameField).sendKeys(username);<br>    }<br><br>    public void setPasswordField(String password){<br><br>        driver.findElement(passwordField).sendKeys(password);<br>    }<br><br>    public ProductsPage clickLoginButton(){<br>        driver.findElement(loginButton).click();<br>        return new ProductsPage(driver);<br>    }<br>}</pre><p><strong><em>findElement Command</em></strong></p><p>This command returns a WebElements.</p><p>After instantiating a WebDriver, we use this command to find WebElements on the page.</p><p><strong><em>SendKeys Command</em></strong></p><p>This method simulates typing into an element and returns nothing.</p><p>In setUserNameField and setPasswordField methods, sendKeys command simulating the typing Username and Password Fields in elements.</p><p><strong><em>getText Command</em></strong></p><p>This method fetches the visible innerText of the WebElement and returns a String Value.</p><p>This command can be useful for asserting negative test scenarios like failed login attempts due to invalid usernames and passwords.</p><p>After getting rejected from the request, there will be an alert text that represents the reject reason for verifying these scenarios.</p><p>So in getErrorAlert method, the getText command fetches the InnerText from the alert due to failed login attempts.</p><p><strong><em>click Command</em></strong></p><p>This command simulates the clicking of any elements. It takes nothing as a parameter and returns nothing.</p><p>In LoginPage class, click a login button.</p><pre>public ProductsPage clickLoginButton(){</pre><pre>driver.findElement(loginButton).click();</pre><pre>return new ProductsPage(driver);</pre><pre>}</pre><p>Since after successful login browser navigates to Products Page, clickLoginButton implemented as returning new Products Page. This is also POM pattern design practice.</p><p>In the test layer, for login tests, the possible test scenarios are;</p><p>1- Successfully Login</p><p>2- Login request rejected for invalid username</p><p>3- Login request rejected for invalid password</p><p>4- Login request rejected for not entering any username and password. Fields are required.</p><blockquote>These all cases have common operations to launch the browser and navigate to the “https://www.saucedemo.com/&quot; site. Also, close the browser after all tests.</blockquote><p>For this reason, LoginTests class was implemented with @BeforeClass and @AfterClass annotations for performing these common operations rather than writing for all test cases in that class.</p><pre>public class LoginTests {<br><br>    private WebDriver driver;<br>    private LoginPage loginPage;<br><br>    @BeforeClass<br>    private void setUp(){<br>        System.<em>setProperty</em>(&quot;webdriver.chrome.driver&quot;, &quot;resources/chromedriver.exe&quot;);<br>        driver = new ChromeDriver();<br>        driver.get(<em>LOGIN_URL</em>);<br>        loginPage = new LoginPage(driver);<br>        driver.manage().window().fullscreen();<br>    }<br><br>    @AfterClass<br>    private void tearDown(){<br>        driver.quit();<br>    }<br><br>    @Test<br>    public void testNullUsernameandPassword(){<br><br>        loginPage = new LoginPage(driver);<br>        loginPage.setUsernameField(<em>NULL_USER</em>);<br>        loginPage.setUsernameField(<em>NULL_PASS</em>);<br>        loginPage.clickLoginButton();<br>        <em>assertEquals</em>(loginPage.getErrorAlert(),&quot;Epic sadface: Username is required&quot; ,<br>                &quot;Null Username and Password test Failed&quot;);<br><br>    }<br><br>    @Test<br>    public void testWrongUsername(){<br><br>        loginPage.setUsernameField(<em>FAIL_USER</em>);<br>        loginPage.setPasswordField(<em>DEFAULT_PASS</em>);<br>        loginPage.clickLoginButton();<br>        <em>assertEquals</em>(loginPage.getErrorAlert(), &quot;Epic sadface: Username and password do not match any user in this service&quot;,<br>                &quot;Wrong Username test failed&quot;);<br><br>    }<br><br>    @Test<br>    public void testWrongPassword(){<br><br>        loginPage.setUsernameField(<em>DEFAULT_USER</em>);<br>        loginPage.setPasswordField(<em>FAIL_PASS</em>);<br>        loginPage.clickLoginButton();<br>        <em>assertEquals</em>(loginPage.getErrorAlert(), &quot;Epic sadface: Username and password do not match any user in this service&quot;,<br>                &quot;Wrong Password Test Failed&quot;);<br><br>    }<br><br>    @Test<br>    public void testSuccesfulLogin(){<br>        loginPage.setUsernameField(<em>DEFAULT_USER</em>);<br>        loginPage.setPasswordField(<em>DEFAULT_PASS</em>);<br>        ProductsPage productsPage = loginPage.clickLoginButton();<br>        <em>assertEquals</em>(productsPage.getPageTitle(), &quot;PRODUCTS&quot;, &quot;Login Failed&quot;);<br>        LoginPage loginPage = productsPage.returnLoginPage();<br>    }<br>}</pre><p><strong><em>Using Inheritance in Automation Framework</em></strong></p><p>For accessing all other pages, firstly, login should be successful. In addition, after the login page, the other pages have elements in common. These are Burger Menu and Shopping Cart buttons.</p><p>So, in the both automation and test layer, BasePage and BaseTests classes are implemented. BasePage class includes common elements within pages, and BaseTests class launches the browser, entering the valid username and password fields, clicking the login button, and navigating the products page. After tests are completed close the session.</p><p>In the test layer, other pages tests extend the BaseTests class.</p><p>Also, the automation layer of the other pages extends BasePage class. This prevents code redundancy and duplication.</p><pre>public class BasePage {<br><br>    private WebDriver driver;<br>    protected By burgerButton   = By.<em>xpath</em>(&quot;//div[@class=&#39;bm-burger-button&#39;]&quot;);<br>    protected By allItems       = By.<em>id</em>(&quot;inventory_sidebar_link&quot;);<br>    protected By about          = By.<em>id</em>(&quot;about_sidebar_link&quot;);<br>    protected By logout         = By.<em>id</em>(&quot;logout_sidebar_link&quot;);<br>    protected By resetAppState  = By.<em>id</em>(&quot;reset_sidebar_link&quot;);<br>    protected By closeBurgerButton = By.<em>xpath</em>(&quot;//div[@class=&#39;bm-cross-button&#39;]&quot;);<br>    protected By shoppingCart   = By.<em>xpath</em>(&quot;//a[@class=&#39;shopping_cart_link&#39;]&quot;);<br><br><br><br>    public BasePage(){<br>        this.driver = driver;<br>    }<br>}</pre><pre>public class BaseTests {<br>    private WebDriver driver;<br>    protected LoginPage loginPage;<br>    protected ProductsPage productsPage;<br><br>   @BeforeClass<br>   public void setUp(){<br>       System.<em>setProperty</em>(&quot;webdriver.chrome.driver&quot;, &quot;resources/chromedriver.exe&quot;);<br>       driver = new ChromeDriver();<br>       driver.get(<em>LOGIN_URL</em>);<br>       loginPage = new LoginPage(driver);<br>       loginPage.setUsernameField(<em>DEFAULT_USER</em>);<br>       loginPage.setPasswordField(<em>DEFAULT_PASS</em>);<br>       loginPage.clickLoginButton();<br>       productsPage = new ProductsPage(driver);<br>       driver.manage().window().fullscreen();<br>   }<br><br>   @AfterClass<br>    public void tearDown(){<br>       driver.quit();<br>   }<br><br>}</pre><p>The parameters like valid username and password, products names and sorting options in the products page, the package name utils, and Config class implemented for managing and maintenance test parameters more efficiently.</p><pre>public class Config {<br>    //Login Tests Data<br>    public static final String <em>LOGIN_URL    </em>= &quot;https://www.saucedemo.com/&quot;;<br>    public static final String <em>DEFAULT_USER </em>= &quot;standard_user&quot;;<br>    public static final String <em>DEFAULT_PASS </em>= &quot;secret_sauce&quot;;<br>    public static final String <em>NULL_USER    </em>= &quot;&quot;;<br>    public static final String <em>NULL_PASS    </em>= &quot;&quot;;<br>    public static final String <em>FAIL_USER    </em>= &quot;wrong_user&quot;;<br>    public static final String <em>FAIL_PASS    </em>= &quot;wrong_pass&quot;;<br>    //Products Data<br>    public static final String <em>SAUCE_LABS_BACKPACK </em>= &quot;Sauce Labs Backpack&quot;;<br>    public static final String <em>SAUCE_LABS_BIKE_LIGHT </em>= &quot;Sauce Labs Bike Light&quot;;<br>    public static final String <em>SAUCE_LABS_BOLT_TSHIRT </em>= &quot;Sauce Labs Bolt T-Shirt&quot;;<br>    public static final String <em>SAUCE_LABS_BOLT_FLEECE_JACKET </em>=&quot;Sauce Labs Fleece Jacket&quot;;<br>    public static final String <em>SAUCE_LABS_ONESIE </em>=&quot;Sauce Labs Onesie&quot;;<br>    public static final String <em>SAUCE_TEST_TSHIRT_RED </em>=&quot;Test.allTheThings() T-Shirt (Red)&quot;;<br>    //Sort Products Options Data<br>    public static final String <em>NAME_A_TO_Z </em>= &quot;az&quot;;<br>    public static final String <em>NAME_Z_TO_A </em>= &quot;za&quot;;<br>    public static final String <em>PRICE_LOW_TO_HIGH </em>= &quot;lohi&quot;;<br>    public static final String <em>PRICE_HIGH_TO_LOW </em>= &quot;hilo&quot;;<br>}</pre><p>In Conclusion, a brief introduction to Selenium WebDriver, WebElements and how to interact with them, how to use effectively inheritance in the automation framework is discussed in part 1 of this article series.</p><p>The series will continue using different interfaces on WebDriver and TestNG functionalities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d75378c09b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Introduction to Behaviour Driven Development(BDD) — Part 1]]></title>
            <link>https://medium.com/@gokcemusul/an-introduction-to-behaviour-driven-development-bdd-part-1-856f3814159f?source=rss-e9178517955b------2</link>
            <guid isPermaLink="false">https://medium.com/p/856f3814159f</guid>
            <category><![CDATA[behavior-driven-dev]]></category>
            <category><![CDATA[bdd]]></category>
            <category><![CDATA[bdd-development]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[cucumber]]></category>
            <dc:creator><![CDATA[Gokcemusul]]></dc:creator>
            <pubDate>Wed, 29 Dec 2021 18:04:39 GMT</pubDate>
            <atom:updated>2021-12-29T18:04:39.005Z</atom:updated>
            <content:encoded><![CDATA[<h3>An Introduction to Behaviour Driven Development(BDD) — Part 1</h3><p>The first part of this technical writing series focuses on a basis of the behavior-driven development process, key aspects of BDD, and differences between test-driven development.<br>The next article will be a practical example of BDD implementing Cucumber and Java.</p><p><strong><em>What is Behavior-Driven Development?</em></strong><br>Behaviour Driven Development is an agile software development process that encourages collaboration to close the gap between business teams and technical teams.<br>The key aspect of behavior-driven development is collaboration. Also, it facilitates software testing because it focuses on testing software behavior<br>from the perspective of well-understood and well-defined software features written in business language, and it encourages the team to use concrete examples or well-defined business rules or scenarios.<br>In addition, it test-first approach is like test-driven development, where you implement a system feature after the test case of that feature is already written.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*efbCP9decpAapk6q7RVR4A.jpeg" /></figure><p><strong><em>Principles of BDD</em></strong><br>BDD encourages working collaboratively across teams. As a result, with simple languages to be used, business teams can read a test and understand what is testing.<br>Tests are often written from the customer’s point of view; is focusing on the user’s interactions with a product with concrete examples.<br>Test-first approach. Firstly, a test set is defined for a unit first. Tests fail. Implement the unit. Return this cycle until the implementation of the unit make the tests succeed.</p><p><strong><em>Concrete Examples, The ‘Given-When-Then’ formula</em></strong><br>A BDD scenario is a written description of your product’s behavior from one or more users in terms of user stories.<br>The following example is about the cancellation of an order in a shopping store</p><p>Title: Cancellation of an order<br>Condition: Logged in<br>Action: Cancel order<br>Outcome: order canceled.<br>BDD acceptance criteria for this scenario can be defined as:<br>Given: User logged in<br>When: User cancel the order<br>Then: Order canceled</p><p>Questions like;<br>The user trying to cancel the order that is already shipped?<br>Is this a duplicate cancel request?<br>Did the user log in before entering the cancel request of order?<br>Splits the feature into multiple scenarios. By these scenarios, a behavior-driven development approach facilitates the coverage of user stories, use cases, and requirement specifications.</p><p><strong><em>Concrete Examples, Role-Feature-Reason Matrix</em></strong><br>This structure is also used in BDD to facilitate user story creation.<br>As an X<br>I can / want Y<br>So that Z</p><p>BDD acceptance criteria for this scenario can be defined as:<br>As a user logged in<br>User canceled an order<br>Order canceled</p><p><strong><em>Traditional Requirement Analysis vs Requirement Specification in BDD</em></strong><br>Traditional Requirement Analysis Techniques include software requirement specifications, use cases, or user stories.<br>In these techniques, business teams tell business needs to product owners, and product owners write requirements, user-system interactions, and specifications.<br>Although these techniques are very useful and applicable for many cases, one key problem with this approach is that specifications are open to interpretation.<br>We can define requirements more explicitly but this requires extra effort.<br>In behavior-driven development approach business teams and technical teams talk about business needs, collaborate around requirements and create well-documented concrete examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R6AS-SG6kjKjeC9NM85ZPQ.jpeg" /></figure><p><strong><em>Test-Driven Development vs Behavior Driven Development</em></strong><br>In a test-driven development method, you write a test case first, then code to fix compilation errors. As a result, the test case would be satisfied by your newly implemented code.<br>You keep refactoring and repeating this approach until your system is fully functional.<br>BDD uses a test-first methodology that is an extension of TDD and works at a higher level of abstraction than TDD.<br>While TDD focuses on reducing the developer’s bias toward the quality of their code and correctness of its working, BDD focuses on covering all possible scenarios, whys of user stories,<br>and facilitates and encourages collaboration between the “three amigos” of software development, business domain experts, developers, and QA testers and automation testers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=856f3814159f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>