<?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 Sherif Rashed on Medium]]></title>
        <description><![CDATA[Stories by Sherif Rashed on Medium]]></description>
        <link>https://medium.com/@sherif.rashed?source=rss-1ab831f303fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JKm8Ij_ekQFLuPOe.</url>
            <title>Stories by Sherif Rashed on Medium</title>
            <link>https://medium.com/@sherif.rashed?source=rss-1ab831f303fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:18:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sherif.rashed/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[Test Driven Development, Geting Started!]]></title>
            <link>https://medium.com/tech-tajawal/driven-development-133422e0057a?source=rss-1ab831f303fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/133422e0057a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[Sherif Rashed]]></dc:creator>
            <pubDate>Thu, 24 May 2018 10:20:28 GMT</pubDate>
            <atom:updated>2018-06-26T08:04:02.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iNSZRtbA3YHmZmjgeBe7MA.png" /></figure><p>In this post, you will know the difference between <strong>TDD, DDD, KDD, and BDD</strong></p><h3><strong>Test Driven Development (TDD)</strong></h3><ul><li>Test-driven development is a development concept when the tests are written before the code. In practical, Developer start the development process by writing unit-test before writing actual code implementation.</li><li>By doing this, we ensure that However the code implement, It’s not affecting the final goal.</li><li>TDD was introduced by XP (Extreme Programming) is an agile software development framework</li></ul><p><strong><em>TDD Cycle</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*UcGzy1kcqcI4ZG-NsXMxjA.png" /><figcaption>TDD Cycle</figcaption></figure><pre>After each test, refactoring is done and then the same or a similar test is performed again. The process is iterated as many times as necessary until each unit is functionally working as expected</pre><p><strong>Example of TDD</strong></p><p>Given the below requirement:</p><ul><li><strong>The password should be between 5 to 10 characters</strong></li></ul><p>To do this in TDD style, we will start by writing the unit test to cover this requirement we should do the below :</p><p>First, we write the test code :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4de7f0cf485ea9d47fccd88f677155ac/href">https://medium.com/media/4de7f0cf485ea9d47fccd88f677155ac/href</a></iframe><p>Actually “<strong>PasswordValidator”</strong> class not created yet so in case of executing the “<strong>TestPassword” </strong>the test will fail.</p><p>Now we will write our code which covers the mentioned requirement</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff696b4bf5485500f172d9e3099bfb8c/href">https://medium.com/media/ff696b4bf5485500f172d9e3099bfb8c/href</a></iframe><p>Now we will run the test by executing the “TestPassword” class, the test will pass as the password length ≥5 &amp;&amp; ≤ 10 (ABC123), in addition, will should try another case for example we should try with password length &lt; 5 , and &gt;10 to make sure that our code works fine.</p><h3>Data-Driven Development (DDD)</h3><ul><li>Data-driven development is a style of development where the data is entered into a database or in an excel spreadsheet and referenced in the automation.</li><li>This allows automation engineers to have a single test script which can execute tests for all the test data in the table/spreadsheet, ..etc.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*x43o_fZ9TKmygIcYLLYO7w.png" /><figcaption>Data Driven Testing Framework</figcaption></figure><p><strong>Why Data Driven Testing?</strong></p><p><em>Consider that we want to test the system login function with multiple input fields with 1000 different data sets, to test this we can take the following different approaches :</em></p><ul><li><strong><em>Create 1000 scripts one for each dataset and run each test separately one by one</em></strong></li><li><strong>Manually change the value in the test script and run it several times</strong></li><li><strong>Import the date from a the data source the use it one by one</strong></li></ul><p><em>In the three previous approaches the first, second approaches are laborious and time-consuming, therefore it is ideal to follow the third approach</em></p><p><strong>Data Driven Testing Example</strong></p><ol><li>Create an excel/CSV with the input test date like the below :</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Svrc8iaB6fGzeUo7zMfG-Q.png" /><figcaption>DDD Table</figcaption></figure><p>2. Create test script :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1eb0bbc0e9ab07b575ebce64529cd5ce/href">https://medium.com/media/1eb0bbc0e9ab07b575ebce64529cd5ce/href</a></iframe><h3>Keyword Driven Development (KDD)</h3><p>Keyword driven development is a style of development where the keywords are entered into a database or in an excel spreadsheet and referenced in the automation.</p><p>It’s important to note that the keywords are mapped to a function.</p><p><strong>Example : Login</strong></p><p>In this case our keyword is ‘login’ and we will map it to a function fnLogin,This function will contain code logic for login functionality.</p><h3><strong>KDD Components</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*S0TUdbimJ_hoAtgrOiyzSw.png" /><figcaption>KDD Components</figcaption></figure><ul><li><strong>Excel Sheet: </strong>will contain the keyword, The keywords can be arranged horizontally or vertically as per your wish</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3FPjZ13Ql9BSa4T-55JKOw.png" /><figcaption>KDD Excel Sheet Example</figcaption></figure><ul><li><strong>Function Library</strong>: read the excel sheets and call the different functions based on the Keywords</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/264/1*uSoBHayFYFg8p1f8vx4I5w.png" /></figure><ul><li>In the Keyword Driven Framework, the operations of the function library can be broadly classified into the following two types:</li></ul><p><strong><em>Application Related Flow</em></strong>: the function library contains functions such as Login and Logout which are actually a part of the application under test</p><p><strong><em>Framework Related Flow</em></strong>: the function library contains functions that are not directly related to the application but related to the framework such as the functions which read keyword from excel</p><ul><li><strong>Data Sheets</strong> : to store the test data that will be used in the application</li><li><strong>Object</strong> <strong>Repository : c</strong>ontain the page objects selectors</li><li><strong>Test Script</strong>: In the keyword driven framework, the keywords, and the flow of the test case are actually specified in the excel sheets since the flow of the test case is mentioned in excel sheets, the actual test script will not store the test case flow. Hence the test script will not be used the way we do it in other framework types such as <strong>functional</strong><a href="http://www.automationrepository.com/2012/04/qtp-framework-tutorial-using-qtp-modular-framework/"><strong> </strong></a><strong>decomposition framework</strong> which create the functions and then save them in the function library.Then we will create a test script where we will call all these functions one after the other</li></ul><p>So in this case, the test script would be used as a driver script whose sole purpose would be to pass the control on to the function library</p><p><strong>KDD Flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*69ReqnPmapvlss8SB__Wqw.png" /><figcaption>KDD Flow</figcaption></figure><ul><li>Test script will call the main function library</li><li>The function library open the excel sheet and reads the first keyword associated with the test case</li><li>The function library calls the function associated with this keyword</li><li>The function then performs all the required actions on the application that is being tested</li><li>Control returns back to main function (in Step 2) which then reads the next keyword. Steps 2 to 5 are repeated till all the keywords associated with a particular test case are called</li></ul><h3>Behavior Driven Development (BDD)</h3><ul><li>Behaviour Driven testing is an extension of TDD. Like in TDD, in BDD also we write tests first and then add application code. The major difference that we get to see here is tests are explained as a behaviour of the application and are more user-focused</li><li>The primary reason to choose BDD as your development process is to break down communication barriers between business and technical teams</li><li>BDD has its own evolution from the days it was born, started by replacing “test” to “should” in unit tests, and moving towards powerful tools like Cucumber and Behat, which made user stories (human readable text) to be executed as an acceptance test</li><li>The idea of story BDD can be narrowed to describe features in a scenario with a formal text, use examples to make abstract things concrete, implement each step of a scenario for testing and write actual code implementing the feature</li><li>By writing every feature in User Story format that is automatically executable as a test we ensure that: business, developers, QAs and managers are in the same boat</li><li>Each feature of a product should be born from a talk between business (analysts, product owner), developers and QAs which are known in BDD as “three amigos”, Such talks should produce written stories there should be an actor that doing some things, the feature that should be fulfilled within the story and the result achieved</li></ul><p>We can try to write such simple story:</p><pre>As a customer I want to buy several products<br>I put first product with $600 price to my cart<br>And then another one with $1000 price<br>When I go to checkout process<br>I should see that total number of products I want to buy is 2<br>And my order amount is $1600</pre><p>Now to execute this story we need to transform it to correct model software , so <a href="http://cucumber.io/">Cucumber</a> introduced a special language for such stories called <strong>Gherkin</strong>. Same story transformed to Gherkin will look like this:</p><pre><strong>Feature</strong>: checkout process<br>  In order to buy products<br>  As a customer<br>  I want to be able to buy several products<br><br>  <strong>Scenario</strong>:<br>    Given I have product with $600 price in my cart<br>    And I have product with $1000 price<br>    When I go to checkout process<br>    Then I should see that total number of products is 2<br>    And my order amount is $1600</pre><p>Cucumber, Behat, and sure, Codeception can execute this scenario step by step as an automated test. Every step in this scenario requires a code which defines it.</p><p>To learn some more about Gherkin format and how to execute it with Codeception check this link <a href="https://codeception.com/docs/07-BDD">https://codeception.com/docs/07-BDD</a></p><p>If you like the concept of Behavior Driven Development or prefer to keep test scenarios in human readable format, Codeception allows you to write and execute scenarios in Gherkin. Feature files is just another test format inside Codeception, so it can be combined with Cept and Cest files inside the same suite. Steps definitions of your scenarios can use all the power of Codeception modules, PageObjects, and StepObjects</p><p>To learn more about Codeception check this link <a href="https://codeception.com/">https://codeception.com</a></p><p><strong>Note</strong>: Usually, in the QA industry, you will find a hybrid of the methodologies explained above</p><p>References :</p><ul><li><a href="https://codeception.com/">Codeception</a></li><li><a href="https://epicqa.wordpress.com/2013/12/21/tdd-bdd-kdd-ddd/">TDD, BDD, KDD, DDD</a></li><li><a href="https://www.softwaretestinghelp.com/">Software Testing Help</a></li><li><a href="https://www.guru99.com/software-testing.html">Software Testing Tutorial</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=133422e0057a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-tajawal/driven-development-133422e0057a">Test Driven Development, Geting Started!</a> was originally published in <a href="https://medium.com/tech-tajawal">tajawal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Testers, Our Training Strategy !]]></title>
            <link>https://medium.com/tech-tajawal/new-testers-training-strategy-76e5d7d1baae?source=rss-1ab831f303fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/76e5d7d1baae</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Sherif Rashed]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 14:24:32 GMT</pubDate>
            <atom:updated>2018-05-27T11:03:01.108Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*mXh_tLXOHzX4tSHsMiuXcw.jpeg" /></figure><p>In this article, you will know more about our new testers training strategy:</p><blockquote><strong>Know Their Background</strong></blockquote><p>Firstly, make sure you know about your new tester technical background!</p><ul><li>Do they have any previous testing experience?</li><li>Have they worked in another technical role, like a developer or support position?</li><li>Do they have domain knowledge?</li><li>What kind of testing things do they love or hate doing?</li><li>Understand why they joined the team and their career goals?</li></ul><p>Knowing the answers to these questions can help you to pitch any training you give at the right level and work out what level of supervision is needed. Are you training someone how to be a tester? Or building on their existing testing experience to fit into their new role?</p><blockquote>Explore The Product</blockquote><p>Letting a new starter get their hands on the product as soon as possible is a great jumpstart to learning it. Encourage them to ask questions so they build their understanding.</p><ul><li>Allocate time for new testers to work through an initial exploratory session, mapping out the main features of the product. By the end of the session they should have some insight into where information can be changed, potential risk areas, and how the product interacts with other systems. Ask them to explain to you what they have discovered.</li><li>You might have product documentation. A getting started guide, product help files, an internal wiki or knowledge base, containing all sorts of useful product information. Make sure new testers know how to access this.</li><li>If the product requires installation or configuration, or test environments need to be set up from scratch, ask them to work through this process. It may help them see what the different components of the product are and how they fit together. They can use this knowledge to develop their own models of the product to assist them in testing.</li><li>Provide details of how to access any log files which might be part of the product.</li><li>Product demos will help them see how the product is meant to be used.</li><li>An overview of upcoming product releases and goals can help a new starter get a feel for where the software is going and the company vision.</li><li>Share stories on successes and failures your product and team have had. It could really help the new tester avoid unnecessary effort or mistakes.</li></ul><blockquote>Get Them Thinking Like A Tester</blockquote><p>The best way to learn how to test and become familiar with a product is by doing some testing. While it might be tempting to assign a list of test cases for your new tester to run, this might not help them to learn how to explore and question the product. A lot of good testers have a curiosity which leads them to ask ‘I wonder what happens if….’ and inexperienced team members need to be encouraged to develop this. Make sure you provide positive feedback and constructive criticism, at all stages.</p><ul><li>Assign them an existing feature of the product to test where you know there are issues. Explain how they could use a testing charter to focus their efforts and ask them to document the testing they do. If they find some of the issues but not others, suggest how they might generate other test ideas which might enable them to uncover these bugs.</li><li>When they find a bug ask them to reproduce the issue and investigate it. Have they discovered the circumstances under which it occurs? Can they hypothesise as to what might be causing the problem, isolate it, then refine the information they have?</li><li>Ask them to write up a bug report for one or more of the issues they found. Give examples from your bug tracking system of what you would class as a good bug report. And of course, make sure the bug hasn’t already been raised.</li><li>Ask them to create a mind map showing how they might test a feature. Do they focus on functionality only? Do they consider Performance? Security? Usability? Do they perform tests below UI level? Do they suggest any tools they could use?</li><li>Schedule pair testing sessions with other members of the team. No matter how much experience a tester has they can learn from these.</li><li>When they start testing new features, review the testing they do. Make sure they aren’t just confirming the acceptance criteria or requirements.</li><li>Assign them bug fixes to retest and ask them to explain how they tested these. Do they focus only on the described steps or explore around the problem?</li><li>Explain what oracles and heuristics are and how these can assist them.</li></ul><blockquote>Start To Build Up The Technical Stuff</blockquote><p>Your team might use all sorts of technical skills to test the product, and by technical I don’t just mean writing automated checks, important as these may be. There are so many different technical skills we might use as testers, think about some of the others too.<br> <br>What tools do you use to aide testing? Browser tools, add ons, proxies, or system tools are some examples. Ask your new tester to spend some time finding out about them and how they work if they don’t already know. Share how they are used in your context and why they support the testing effort. Demonstrate any important tools and how to use them to make sure sufficient information is gathered during testing.</p><p>You might also want to consider the following:</p><ul><li>Databases — Ensure they know how to view or manipulate information in any databases you might use as part of testing.</li><li>API testing — If your new tester has not tested without a UI before they’ll need to know how to explore an API and interpret the responses.</li><li>Security — An important consideration in all application types. What techniques need to be used here?</li><li>Performance — What are the performance requirements for the product and how are these tested?</li><li>Programming — Where automated checks are a priority, provide resources to help them get started with the necessary programming language.</li><li>Automation framework — If they do have programming experience, walk through how your framework is put together. Ask them to pair with another tester to create some automated checks and perform a code review.</li></ul><blockquote>Get them know the processes</blockquote><p>The processes we use can make a huge difference to the outcome of a project, so new starters will need to get to know how they should be working. The following are some things you might want to consider:</p><ul><li>Get them involved in team or sprint meetings as soon as possible, they will get to know the team members, their different roles and the way you all work together.</li><li>Make sure they understand the purpose of these meetings, perhaps they are new to an agile methodology and could be standing there wondering ‘Why do we need to do this?’.</li><li>Let them spend some time sitting with a developer so they can see what they are working on. Do they write unit tests? Do testers contribute to this process?</li><li>Where do automated checks fit into the testing process?</li><li>You might use Continuous Integration, explain this process and it’s benefits.</li><li>Are there standards or legislation your team must comply with?</li><li>How does the team prioritise bugs? Is it the responsibility of the tester or a whole team activity?</li><li>How is testing recorded? Provide examples of how your team does this and give feedback on testing they document.</li></ul><p>As testers we’re always looking for new ways of doing things and when a new person with a fresh perspective joins a team they will often ask questions which can make us re-evaluate our process and even lead to improvements. Where you are involved in training new testers you should make sure to let them know they shouldn’t be afraid to suggest new ways of working, and how participating in things like retrospectives can facilitate this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76e5d7d1baae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-tajawal/new-testers-training-strategy-76e5d7d1baae">New Testers, Our Training Strategy !</a> was originally published in <a href="https://medium.com/tech-tajawal">tajawal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>