<?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 Sankha Jayasooriya on Medium]]></title>
        <description><![CDATA[Stories by Sankha Jayasooriya on Medium]]></description>
        <link>https://medium.com/@sankha.jayasooriya?source=rss-d5ba487cefef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Jrq2vKWW5ndnG0_K.jpg</url>
            <title>Stories by Sankha Jayasooriya on Medium</title>
            <link>https://medium.com/@sankha.jayasooriya?source=rss-d5ba487cefef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:00:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sankha.jayasooriya/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[Achieving Maximum Test Coverage : Chapter 2 — “Functional Specification Data Mapping”]]></title>
            <link>https://medium.com/genius-quality/achieving-maximum-test-coverage-chapter-2-functional-specification-data-mapping-86e5657aed3e?source=rss-d5ba487cefef------2</link>
            <guid isPermaLink="false">https://medium.com/p/86e5657aed3e</guid>
            <category><![CDATA[sankha-jayasooriya]]></category>
            <category><![CDATA[test-coverage]]></category>
            <category><![CDATA[functional-specifications]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Sankha Jayasooriya]]></dc:creator>
            <pubDate>Fri, 25 Jan 2019 14:06:02 GMT</pubDate>
            <atom:updated>2019-01-31T12:26:07.155Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Achieving Maximum Test Coverage: Chapter 2 — “Functional Specification Data Mapping”</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oTK_1EtboUrZ0IGqCiWjqA.jpeg" /></figure><p>In our Journey to Achieving Maximum Test Coverage, we have discussed Mind Mapping in the last chapter. Here’s the <a href="https://medium.com/genius-quality/achieving-maximum-test-coverage-chapter-1-mind-mapping-5c522ab7ffa4">Link</a> to who have missed.</p><p>In this chapter, let’s discuss the Functional Specification Data Mapping which is also known as FSDM.</p><p>First, let’s Identify the fields in FSDM sheet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_dOA7W3hSSNuQsC25S2pyA.png" /><figcaption>Sample Functional Specification Data Mapping Sheet</figcaption></figure><p><strong>1</strong>. <strong>Feature:</strong> Feature name of the function to be described</p><p>Ex: Sign in to Gmail account</p><p><strong>2</strong>. <strong>Feature Reference:</strong> Reference to the Requirement ID</p><p>Ex: JIRA Ticket ID</p><p><strong>3</strong>. <strong>Impacting Conditions:</strong> Common facts or conditions to be fulfilled before starting the testing. Consider conditions that hold tester from moving forward with testing without setting up.</p><p><strong>4</strong>. <strong>Common Preconditions:</strong> Preconditions for the software under test.</p><p>Ex: Active User should be login to the system</p><p><strong>5</strong>. <strong>Variable:</strong> Should include all the visible and hidden factors that effect to the relevant feature.</p><p>Ex:</p><ul><li>Visible factor: Username</li><li>Hidden factors: When uploading an image, format and maximum image size should be taken into consideration</li></ul><p><strong>5.1. Variable Name:</strong> The variable name should be exactly the same as the UI name. In addition, you can add a small note about the specific variable (like variable behavior) within the square brackets</p><p>Ex: UserName [only can add characters]</p><p><strong>5.2. Variable Type:</strong> Identify the type of the variable that you have added as variable, and select it from the drop-down selection</p><p><strong>5.3. Significance:</strong> You have three options as below</p><ul><li>Optional — Variable is an optional one for the specific feature</li><li>Precondition — Variable is going to act as a precondition to the following variables</li><li>Mandatory — Variable is a mandatory one for the specific feature</li></ul><p><strong>5.4. Conditions:</strong> Can use below conditions.</p><ul><li>WHEN — Denotes the existence of a condition in a positive form</li><li>WHENNOT — Denotes an existence of a condition in a negative form</li><li>AND — Logical AND</li><li>OR — Logical OR</li><li># — Denotes the equality sign (=) in a condition</li></ul><p><strong>6. Value:</strong> You can add the possible input space for the relevant variable</p><p><strong>6.1. Value Descriptions:</strong> Add all the possible values related to the variable. Use the Technics like boundary value analysis, equivalence partitioning. In the end, you can identify the test input space of each variable of the feature.</p><p><strong>6.2. Value Type:</strong> Identify the data type of the value</p><p><strong>6.3. Group:</strong> Group values, so that user is allowed to apply conditions for a set of values.</p><p><strong>6.4. Value Conditions:</strong> Here you can specify whether the specific value description is depending on some other variable description(s) or not. Same conditions can be used here as well.</p><ul><li>WHEN — Denotes the existence of a condition in a positive form</li><li>WHENNOT — Denotes an existence of a condition in a negative form</li><li>AND — Logical AND</li><li>OR — Logical OR</li><li># — Denotes the equality sign (=) in a condition</li></ul><p><strong>7. Status:</strong> Can specify the status. But only if the corresponding values — conditions combination makes the expected result FAIL</p><p><strong>8. Importance:</strong> Mark the priority of each value — conditions combination.</p><p><strong>9. Expected Result:</strong> It is not mandatory to provide the expected result for all the combinations, but make sure to provide the expected result for all the FAIL combination. Always give the highest priority to FAIL occurrences when adding expected results.</p><p><strong>10. Remarks:</strong> You can add any special comment related to the variable or a specific value in this field</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vPc-V4AW86U88NHb7-clzA.jpeg" /></figure><p>Now let’s look at the <strong>Golden Rules</strong> to be followed when filling the FSDM.</p><ul><li>Table structure should be maintained along the way. Should not be changed for any reason.</li><li>Exact same variable names and value descriptions in conditions (variableName#valueDescription)</li><li>Variable names should be in camel Notation starting with a lower case letter</li><li>Keywords, variable names, and value descriptions are case sensitive. This does not apply to Expected Result and Remark fields</li><li>A value marked with “Fail” can never be a condition to a factor or a value (a rule derived from above logic)</li><li>Value marked with “Fail”, can have conditions which are formed with valid values (the Basic purpose of being allowed to specify conditions)</li><li>When adding conditions at least one positive values should be left out. (This is because we want to leave at least one value so that combinations can be created by using the possible values)</li><li>When denoting “Not Applicable” do not use “N/A” instead use “NA”.</li><li>When using value type as Boolean, use value description as “true” or “false”. Don’t use it as “TRUE” or “FALSE”. (Hint: Format Excel cell as “text”)</li><li>Do not use “&amp;” sign in Feature Name, Feature Description, and Preconditions, instead use ‘and’.</li></ul><p>So now you know the fields on FSDM and how to fill it. In the next chapter, let’s discuss how to derive the variables, values are other dependencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5BSJWd8nHNUMmd-0d1uPQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86e5657aed3e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/genius-quality/achieving-maximum-test-coverage-chapter-2-functional-specification-data-mapping-86e5657aed3e">Achieving Maximum Test Coverage : Chapter 2 — “Functional Specification Data Mapping”</a> was originally published in <a href="https://medium.com/genius-quality">Genius Quality</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Achieving Maximum Test Coverage : Chapter 1 - “Mind Mapping”]]></title>
            <link>https://medium.com/genius-quality/achieving-maximum-test-coverage-chapter-1-mind-mapping-5c522ab7ffa4?source=rss-d5ba487cefef------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c522ab7ffa4</guid>
            <category><![CDATA[sankha-jayasooriya]]></category>
            <category><![CDATA[driving-the-requirement]]></category>
            <category><![CDATA[test-coverage]]></category>
            <category><![CDATA[mind-mapping]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Sankha Jayasooriya]]></dc:creator>
            <pubDate>Thu, 24 Jan 2019 13:39:30 GMT</pubDate>
            <atom:updated>2019-01-31T12:22:42.876Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Achieving Maximum Test Coverage: Chapter 1 - “Mind Mapping”</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lhhhUfY-aYhRJA6mUj3PzQ.jpeg" /></figure><p>Most of the time defects occur in software systems due to not capturing the requirements correctly in early stages of the development life-cycle. When we identify the requirements correctly in later stages, corrective actions will be costlier. All of today’s QA Practices have been focused on Preventing Defects. So let&#39;s discuss how can we do that.</p><p>Finding defects is not QA’s only defined responsibility. If we think about a little what our title implies <strong>“Quality Assurance”,</strong> which is more about assuring overall product quality. Defect finding is only a part of it, but not only limited to it. Everything we can do to assure product quality matters, which starts with quality in the requirement stage. Quality Assurance heavily depends on the information about the product being developed. QA Engineers use this information to perform testing during the development of the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*5OoBPbqFmwblsRyi9zXBcA.jpeg" /></figure><p><strong>Driving the Requirements</strong> is something that everyone emphasizes QA engineers should do as a solution, which nobody knows what does that exactly mean, or have no clue how it’s done. So the question still stands, how can we do that?</p><p>One practical approach that can be followed to address the problems is <strong>Functional Specification Data Mapping</strong>. It is just a simple framework which needs to be followed with a good understanding of the purpose of it. It starts with <strong>Mind Mapping</strong> which I’m gonna cover today. Briefly, the Mind map should be created from a users point of view and features should be included in the grass root level nodes.</p><p>Here is an example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6T9yF-V4b0XDrDw--ORxDw.png" /><figcaption>Sample Mind Map</figcaption></figure><ol><li><em>Root Node — Main Topic (Project/ Use Case Name)</em></li><li><em>Topic Node — Subtopic (Optional) (Feature Name)</em></li><li><em>Parent Node — Any topic that has subtopics branching off of it. (Growing up to granular level features to test)</em></li><li><em>Child Node — Any topic that branches from another topic. (Intermediate nodes up to granular level feature)</em></li><li><em>Boundary — A boundary is a section of nodes that have a clear end. This should be an atomic level of the requirement/feature facts.</em></li></ol><p>There are many free mind mapping tools available. “Free Mind” is my favorite. It’s very simple and practical. And also it’s the platform for many colorful mind mapping tools.</p><p>Something to keep in mind is, if you are sharing your mind map with any particular party for reference, make sure to convert it to a PDF format. Otherwise, they won’t be able to open your file unless they install a compatible mind mapping tool.</p><p>So that’s it for Mind Mapping. Let’s talk more about the Test Coverage in my next chapter with Functional Specification Data Mapping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*xpY7UGAUIlADIzMfpniX0w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c522ab7ffa4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/genius-quality/achieving-maximum-test-coverage-chapter-1-mind-mapping-5c522ab7ffa4">Achieving Maximum Test Coverage : Chapter 1 - “Mind Mapping”</a> was originally published in <a href="https://medium.com/genius-quality">Genius Quality</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing a Mission Critical System : The Way We Do it.]]></title>
            <link>https://medium.com/genius-quality/testing-a-mission-critical-system-the-way-we-do-it-90b0c6c9fdc9?source=rss-d5ba487cefef------2</link>
            <guid isPermaLink="false">https://medium.com/p/90b0c6c9fdc9</guid>
            <category><![CDATA[shift-left-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[api-automation]]></category>
            <category><![CDATA[sankha-jayasooriya]]></category>
            <category><![CDATA[peer-testing]]></category>
            <dc:creator><![CDATA[Sankha Jayasooriya]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 17:30:38 GMT</pubDate>
            <atom:updated>2019-01-31T12:10:28.606Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testing a Mission Critical System: The Way We Do it.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYVNPdnUi9rThFwJ5ippUg.jpeg" /></figure><p>I’m working as an offshore consultant to a tier one retailer in the USA. The Client is a very tough and demanding one. All of the above factors make the project, a mission critical one. So let’s see how we test the system and what are the approaches we take.</p><p>The latest trend in QA Testing call as “<strong>Shift Left Testing</strong>”. Simply put, it’s where we move all the QA related activities into the beginning of the Sprint. On traditional approaches, most of the QA activities begin after the development work is completed. So they were focused on Defect finding. But the cost of fixing those defect will be high. Because all the defects get identified at the end of the sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hof_i253_XXjEiyy5E8MMQ.jpeg" /><figcaption>Advantages of Shift Left Testing</figcaption></figure><p>Since we are moving ahead with modern world concepts and techniques, we are more focus on Defect prevention rather than defect finding. So our work starts in the early stage of the sprint as soon as requirement gathering starts. We are reviewing the User Stories and screen mock-ups prepared by our BA team. And we report if those are not aligned with the requirement or it differs from our understanding of the requirement. We brainstorm with both the Development team and BA team until we get finalized the requirement. The objective of this exercise is to bring all the teams into the same understanding of the requirement.</p><p>While Development team start their design and development, we start our Test Scenario design task parallelly. We use techniques like Mind Mapping and Functional Specification Data Mapping to capture the requirement correctly into our Test Scenarios. Once we completed that, we send them to both Development and BA team for review. If they need we will have walk-through sessions as well. In the meantime, the QA team start to create Test Cases from those Test Scenarios. If there are any alterations or valid feedback from Development or BA team, we incorporate them as well in our test cases. Not only the manual Test Cases but Automation Test Scripting also happening at the same time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gw6u7YbGIIQVoapfqVn_XA.jpeg" /><figcaption>Testing Activities Throughout The Cycle</figcaption></figure><p>With the nature of our application, we are more focused on <strong>API automation</strong>. It covers more ground quickly than UI Automation. So as soon as we get a working environment with the API’s deployed, we start scripting. Most of the time this environment will be a Local Development environment. Once we receive the API documentation, we can finalize our automation scripts by adding the remaining assertions. Since most of the tasks happen parallelly, test case creation and scripting tasks also will be completed by the time of development completes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*U0pWqMMxTDnOW9fue9U9Lg.jpeg" /><figcaption>Peer Testing</figcaption></figure><p>Another important activity we perform is “<strong>Peer Testing</strong>”. We test the underdeveloped application on Local Development environments. Whatever the features that Developers have completed, the QA team does high-level testing on them. We are more focus on the application functionality rather than UI. Of course, if we see an obvious UI issue, we report it. But we pay more attention towards the functionality. Whatever the Issues we find at this phase, we report them quickly to the Development team in a group chat. And also add them to a google sheet for tracking purpose. So we can get them fixed quickly and test the same in a moment, rather than waiting for a whole release cycle to get the Defect Fix release. Since the release is not an official one, whatever the bugs we find do not goes to the official report either. Target is to find and fix the bugs in early stages. This is a very important milestone on the journey towards Defect Prevention.</p><p>After Development team completes the development and unit testing, they are sending an official QA release to the team. We use a common Release Note Template for all the applications, which also a product of QA Team. All most all the API related functionalities have been automated. So we put them to run overnight through our CI environment. In the next morning, we start with verifying the Automation status report and re-run the failed test cases. If we find any issues, they will be tracked in our official defect tracking system. UI testing will be more focus on the happy path since we have covered all the negative test cases through the API automation. So testers will get more time to do the exploratory testing.</p><p>Root Cause Analysis will be done after each major release. We decide whether to go for another deployment or move the defects to the backlog. For this decision, we take into account the facts like severity, the priority of the defects and the importance of the feature and also how frequently this feature will be used in production. And also we maintain a Root Cause Analysis report for each major release. Whatever the mitigation actions that need to be taken will also be included in the same.</p><p>Once the testing work is completed, we share our Test Results with the client. Those are needed to get the managerial approval for the Production Deployment. The deployment will be done by Cloud Ops team, but both Dev and QA Team will participate in the event too. Once the application gets deployed, QA Team does a high-level verification to make sure all the new features are included and already existing functionality isn’t broken.</p><p>This will conclude a successfully Product Deployment.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F4884466&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fcongrats-leonardo-dicaprio-fireworks-the-great-gatsby-old-sport-gif-4884466&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fimages%2F7948ac1931f2d5693a90abf362fb8280%2Fraw&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/7142945212ee08663b4e1a013893847d/href">https://medium.com/media/7142945212ee08663b4e1a013893847d/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90b0c6c9fdc9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/genius-quality/testing-a-mission-critical-system-the-way-we-do-it-90b0c6c9fdc9">Testing a Mission Critical System : The Way We Do it.</a> was originally published in <a href="https://medium.com/genius-quality">Genius Quality</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>