<?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 フエザル (Fais) on Medium]]></title>
        <description><![CDATA[Stories by フエザル (Fais) on Medium]]></description>
        <link>https://medium.com/@faizeals?source=rss-3773ce10caaf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IqOpYQ6Gqmrc_oA2DxW7Iw.png</url>
            <title>Stories by フエザル (Fais) on Medium</title>
            <link>https://medium.com/@faizeals?source=rss-3773ce10caaf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:37:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@faizeals/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[The Fundamental Test Process in Software Testing]]></title>
            <link>https://medium.com/zeals-tech-blog/the-fundamental-test-process-in-software-testing-7da96e1d6e33?source=rss-3773ce10caaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7da96e1d6e33</guid>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[test-planning]]></category>
            <category><![CDATA[qa-automation]]></category>
            <dc:creator><![CDATA[フエザル (Fais)]]></dc:creator>
            <pubDate>Wed, 02 Aug 2023 04:17:09 GMT</pubDate>
            <atom:updated>2023-08-02T04:17:09.363Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*5rr2IhRsXRtsrZr_" /></figure><p>At Zeals, I have recently been working on the entire test process of “Robotic Process Automation,” which refers to automating the process of inputting previously collected information into a target webform at a specified URL and the automation of filling out client forms. So, for this reason, I thought it would be good to explain more about testing, as well as the importance of each step in the testing process.</p><p>Testing, despite common misconceptions, follows a systematic approach. The initial step in this process is test planning, followed by test case creation, execution preparation, and status evaluation, concluding with test closure. Consequently, the essential activities of the test process can be categorized into the subsequent stages:</p><p>1. Planning and Control</p><p>2. Analysis and Design</p><p>3. Implementation and Execution</p><p>4. Evaluating exit criteria and Reporting</p><p>5. Test Closure activities</p><h3>Planning and Control</h3><p><strong>Test planning encompasses several crucial activities:</strong></p><p>· Determining the test approach for conducting the test, in order to ascertain the extent of potential risks, as well as to pinpoint the objectives of testing.</p><p>· Implementing test policies and a test strategy. Test strategy is an outline that describes the testing portion of the software development cycle. It is created to inform PMs, testers, and developers about key issues of the testing process. This includes the testing objectives, method of testing, total time and resources required for the project, and the testing environments.</p><p>· Conducting a comprehensive evaluation to ascertain the necessary resources for testing, such as personnel, testing environments, and computer systems.</p><p>· Arranging the allocation of time for carrying out tasks related to analyzing and designing tests, implementing them, executing them, and evaluating the results.</p><p>· Defining specific criteria known as Exit criteria in order to establish the conditions under which the testing phase can be concluded. These criteria are primarily focused on measuring the extent of coverage, which pertains to the percentage of software statements that must be executed during the testing process. By monitoring these criteria, Testers can assess the accuracy and completeness of testing activities. Additionally, these criteria provide clear guidelines for the tasks and evaluations that must be accomplished at each level of testing before the tester can declare the testing phase as complete.</p><p><strong>The main responsibilities of test control include the following:</strong></p><p>· To assess and analyze the results of reviews and testing.</p><p>· To oversee and record the advancement, scope of testing, and conditions for completion.</p><p>· To provide information on testing.</p><p>· To commence measures aimed at rectifying the situation.</p><p>· To make decisions.</p><h3>Analysis and Design:</h3><p><strong>The primary responsibilities of test analysis and test design encompass the following essential tasks:</strong></p><p>· To review the test basis. The test basis serves as essential information for initiating test analysis and developing customized test cases. It primarily encompasses documentation that forms the foundation for test cases, including requirements, design specifications, product risk analysis, architecture, and interfaces. These test basis documents enable us to gain a comprehensive understanding of the expected functionalities and behavior of the system once it is developed.</p><p>· To ascertain the conditions under which tests should be conducted.</p><p>· To create the tests.</p><p>· To assess the testability of both the requirements and the system, we must conduct a comprehensive evaluation.</p><p>· In order to establish the test environment and determine the necessary infrastructure and tools, we must think about the design process.</p><h3>Implementation and Execution:</h3><p>When conducting the implementation and execution of tests, Testers consider the test conditions and convert them into test cases and procedures, along with other Testware such as automation scripts, the test environment, and any additional testing infrastructure. Test cases are composed of conditions a tester uses to assess an application’s correct functionality. Testware refers to all the tools and resources used for testing software, including scripts, the test environment, and other infrastructure elements that can be reused in the future.</p><p><strong>The implementation of the test involves a set of primary responsibilities.</strong></p><p>· To assess the functionality of a software application, it is necessary to develop and prioritize test cases. These test cases involve the utilization of various techniques to create test data. Test data refers to the information entered during testing to evaluate different features and aspects of the software. Additionally, test procedures are created to provide instructions for conducting the tests. To streamline the testing process, testers may also employ test harnesses and automated test scripts. The test harness is a collection of software and test data that enable the testing of specific program units under varying conditions, allowing for the monitoring of their behavior and outputs.</p><p>· To create test suites from the test cases to streamline the process of conducting tests. Test suites refer to a compilation of test cases designed to evaluate a software program and demonstrate its predetermined set of functionalities. These test suites typically include comprehensive instructions and system configuration details to be employed during testing. Test suites serve the purpose of grouping together test cases that share similar characteristics.</p><p>· To execute and authenticate the setup.</p><p><strong>Test execution has the following significant responsibilities:</strong></p><p>· To carry out test suites and individual test cases in accordance with the specified testing procedures.</p><p>· Confirmation testing or re-testing involves rerunning the tests that failed to verify a fix’s effectiveness.</p><p>· The purpose of logging the test execution results in the software testing process is to document the test cases executed, their order, and the relevant details such as who executed them and their results (pass/fail). This information is recorded in the test log, which serves as an audit trail.</p><p>· To evaluate the achieved outcomes in contrast to the anticipated outcomes.</p><p>· Incidents are reported when there are differences between the actual outcomes and the anticipated outcomes.</p><h3>Evaluating Exit Criteria and Reporting:</h3><p>The risk evaluation of the project will establish the standards, known as exit criteria for each test stage, which will serve as the benchmark for determining the adequacy of testing.</p><p>Exit criteria are relevant in situations where certain conditions must be met to determine when a process or activity can be considered:</p><p>· Most test cases undergo execution with a specific rate of successful completion.</p><p>· Bug rate dips below a specific threshold.</p><p>· When the deadlines have been met.</p><p><strong>Evaluating exit criteria has the following major tasks:</strong></p><p>· To verify the test logs against the predetermined exit criteria outlined in the test planning process.</p><p>· To determine the necessity of additional tests or the need to modify the specified exit criteria.</p><p>· To compose a comprehensive report on test results and findings for stakeholders.</p><h3>Test Closure activities:</h3><p>Test closure activities in software testing are typically performed upon delivery of the software. However, there are various other circumstances where the testing process can be officially concluded.</p><p>· Once all the requisite data has been collected for the testing process.</p><p>· In the event of the termination of a project.</p><p>· When a specific objective is successfully attained.</p><p>· Maintenance releases or updates are conducted.</p><p><strong>Test Closure activities encompass several essential responsibilities:</strong></p><p>· This task verifies the completion of planned deliverables and ensures the resolution of all incident reports.</p><p>· The process of concluding and storing Testware, such as test scripts and test environments, in a formal manner for future reuse.</p><p>· The Testware will be transferred to the maintenance organization, which will provide software support.</p><p>· To assess the outcome of the testing process and extract valuable insights for forthcoming releases and projects.</p><p><strong>CONCLUSION</strong>:</p><p>Testing is a process rather than a single activity. Testing must be planned and it requires discipline to carry it out. Here at Zeals, we believe testing is a fundamental and crucial part of any software project. Following the fundamentals of the testing process, we plan for testing adequately to ensure that the product or service is of the highest quality and meets the requirements of the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7da96e1d6e33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zeals-tech-blog/the-fundamental-test-process-in-software-testing-7da96e1d6e33">The Fundamental Test Process in Software Testing</a> was originally published in <a href="https://medium.com/zeals-tech-blog">The Zeals Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating ‘Zeals’ Calendar Using Selenium WebDriver for Testing]]></title>
            <link>https://medium.com/zeals-tech-blog/automating-zeals-calendar-using-selenium-webdriver-for-testing-c73966adb19?source=rss-3773ce10caaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c73966adb19</guid>
            <category><![CDATA[selenium-webdriver]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[testing-framework]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[フエザル (Fais)]]></dc:creator>
            <pubDate>Thu, 01 Dec 2022 05:18:25 GMT</pubDate>
            <atom:updated>2022-12-01T05:18:25.182Z</atom:updated>
            <content:encoded><![CDATA[<p>A date picker, popup calendar or date time picker regardless of the name, is a graphical user interface widget that allows users to select a date from a calendar.</p><p>Recently at Zeals we have released RPA Post Logs. If you use this feature, you will come across a calendar to pick dates and even times. These calendars make the entire process of choosing dates easier and more interactive and play a significant role in improving user experience.</p><p>As a tester, automating the datepickers in a dynamic way can be an intimidating task. There are several ways to handle calendar controls. Therefore in this testing blog, I will explore a test case that demonstrates how to select a date in Selenium Webdriver using Java.</p><p>Selenium is a widely used automation testing tool with the purpose of ensuring web applications function smoothly and according to specific technical and business requirements.</p><p><strong>Zeals’ Calendars:</strong></p><p>At Zeals we have different type of calendars such as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Izn84fPxDPJiKb38" /></figure><p>This article uses Post Logs [Calendar 1], but the goal is to automate the calendar dynamically, so the basic approach should work for all of Zeals’ calendars.</p><p><strong>Approach to Handling the Calendar:</strong></p><p>If your calendar has editable text fields, it is easier to use input fields. You just have to consider the expected date format. However, in our case, these fields are either disabled or not editable. Therefore, we will be using a different approach.</p><p>If you look at the calendar, once users click the calendar button, they have the option to select the Year / Day / Month of their choice. This Option could be in the past, present, or future. We can think of it as a Target date. For this purpose, I will create a Java Class which handles all the Date picker components. Let’s take a deeper dive into the approach:</p><ul><li>Open the Date Picker / Calendar.</li><li>Get the current Month and Year (this can be accessed via the current month label).</li><li>Compare the current Month and Year to the target Month and Year.</li><li>Find out if the user needs to navigate to the past, future or present to meet the Target date.</li><li>Use the &lt; &gt; component to navigate to the past or future calendar page.</li><li>Select the desired day.</li><li>Finally perform some Tests.</li></ul><p><em>Note: Ideally this approach should work for all the calendars shown above as they have similar components.</em></p><p><strong>Step 1: Create a Calendar Page/Framework</strong></p><p>First create a Class and add different calendar components which will interact with the UI calendar.</p><p>We already have an internal Automation Test Framework, and I will be utilizing some of its features for the initial setup such as Webdriver setup, Login and navigating to the desired calendar destination. I will not be sharing or discussing those features in this blog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*AJhmoTcLYNxo_1ZO" /></figure><p>Within this class, create a class constructor that accepts the Webdriver that needs to interact with the browser and all the elements that they need to interact with. Thanks to our Frontend team for providing nice test-data IDs, which we can use to interact easily with different calendar components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/0*lte43oHO8HeLva6m" /></figure><p><strong>Step 2: Decide the Target Dates / Test Cases</strong></p><p>I will be creating up to Five Test cases. One with past date, one with future date, one with current month date. Our goal is to create a date picker framework which can handle multiple valid dates.</p><p><em>I will be using the date at which Zeals’ founded in (2014年4月1日) for this purpose</em></p><ol><li>(Past Date) 2014 April, 1</li><li>(Future Date) 2023 April, 1</li><li>(Current Date) 2022 Nov, 22</li><li>(Octal Value Test, since we will be Formatting the date) 2022 April, 01</li><li>(Duplicate Value) 2023 Aug, 31</li></ol><p><strong>Step 3: Open the Calendar</strong></p><p>The first thing we need to do is open the date picker. However, it is always a good practice to consider if the Calendar is already opened. It will not be the case with our current Date Picker design. However, since we are trying to create a more dynamic automation framework, we will consider adding a validation to make sure if “click” is required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*wn0aiK5E2VMNpPIN" /></figure><p><strong>Step 4: Get the Current Month/Year</strong></p><p>Now that the date picker is opened, the first thing we need to do is to capture the current Month and Year. This can be easily achieved by reading the calendar Label 2022年11月 and splitting it into an array and using it to create a LocalDate object.</p><p>It is worth mentioning that I will be using a Java LocalDate Class. A LocalDate class is an immutable datetime object representing a date, often displayed as year-month-day. We can also access other date fields, such as day of the year, day of the week, and week of the year. It also allows us to format the date. For example, the value “2014 April, 1” can be stored in LocalDate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/0*AAmkAfI47CURjATK" /></figure><p><strong>Step 5: Compare the Current and Target Month/Year</strong></p><p>Now that we have determined the current Month/Year in the last step, the next thing we need to decide is whether we need to move from the current month to the past or the future. Since the user will be providing the Target dates, in this case we can achieve this goal by comparing the current and target dates.</p><p>Not forgetting the day of the month is yet to be selected. In this step I will set it to the first day of the month, this can be achieved with LocalDate method <strong>withDayOfYear(int dayOfYear)</strong>.</p><p>Here and now, we have a current Date (Year/Month/Day). We can now simply compare the current and Target dates.</p><p><strong>Step 6: Where to? Current, Past, Future!</strong></p><p>Once you have the month difference value, you can identify the month of interest. A negative value is a month in the past, a positive value is a month in the future, and a value of zero is the current month.</p><p><strong>Step 7: Navigate to the Target Month/Year</strong></p><p>Next, we can use the &lt; &gt; arrows to navigate to the desired target Month/Year. Plus, we can control this through a loop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*7o-UWIh-Gu-ZI-80" /></figure><p><strong>Step 8: Select the Desired Day</strong></p><p>Since we are on the Target Month/Year, selecting a day is straightforward. We have the locator and simply click the required day of the month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/0*eTIhHCxpIH_5OzRx" /></figure><p>But if your calendar dates repeat, this implementation won’t work, so don’t get carried away. The Post Logs calendar is fine as it does not contain recurring dates. However, in the following calendar if the target date is August 31, then July 31 will be selected instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/0*xj_OxpLuWJIWda_H" /></figure><p>To make this more dynamic we should consider both cases. Now, if the selector used for the above is again used for implementation, it will not be helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/0*JLASy4UxtSHvmdDY" /></figure><p>Therefore, after reviewing the DOM, we will be changing the locator to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/0*kMztMnwF3XVWMAfW" /></figure><p>Next, we need to modify our setDay method to accommodate the new selector’s value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/0*C2Nn8gLIPDiTTU_R" /></figure><p><strong>Step 9: Testing! Testing! Testing!</strong></p><p>Finally, we will perform the Test on our date picker framework. As shared above we will be running Five tests and as you can see All Tests passed!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*KFW1a9fM-Wlej-ot" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/0*c6ySqnN3-p7BXlaT" /></figure><p><strong>Conclusion</strong></p><p>I hope this tech blog has been useful to you, helping you to understand how to make an automated Calendar using Selenium WebDriver for testing. As mentioned before, these calendars make the entire process of choosing dates easier and more interactive and play a significant role in improving user experience and this particular one incorporates a date picker framework that is both useful and user friendly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c73966adb19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zeals-tech-blog/automating-zeals-calendar-using-selenium-webdriver-for-testing-c73966adb19">Automating ‘Zeals’ Calendar Using Selenium WebDriver for Testing</a> was originally published in <a href="https://medium.com/zeals-tech-blog">The Zeals Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>