<?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[Quality Matters - Medium]]></title>
        <description><![CDATA[We speak about quality, testing, agile, test automation, DevOps, test process and strategy. - Medium]]></description>
        <link>https://medium.com/quality-matters?source=rss----c5cc384cc19d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Quality Matters - Medium</title>
            <link>https://medium.com/quality-matters?source=rss----c5cc384cc19d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:56:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/quality-matters" 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 Strategy in Mobile and Big Screen Testing]]></title>
            <link>https://medium.com/quality-matters/test-strategy-in-mobile-and-big-screen-testing-a206010d0d?source=rss----c5cc384cc19d---4</link>
            <guid isPermaLink="false">https://medium.com/p/a206010d0d</guid>
            <category><![CDATA[casting]]></category>
            <category><![CDATA[big-screen]]></category>
            <category><![CDATA[testing-my-story]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Mariia Hutsuk]]></dc:creator>
            <pubDate>Thu, 08 Apr 2021 16:29:15 GMT</pubDate>
            <atom:updated>2021-04-08T17:06:27.712Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>This story is co-authored together with </em><a href="https://medium.com/u/827cc9350bfb?source=post_page-----f55fc40439c6--------------------------------"><em>Sivamoorthy Bose</em></a></p><p>At the moment the software applications become an integral part of our daily lives. QAs are the most familiar with web based application testing, however there are much more other types of applications. In this article we would share our experience of testing mobile, STB, big screen and casting applications.</p><h3>Mobile</h3><p>Usage of Smartphones have been increasing these years. Businesses are now focusing on integrating and delivering mobile applications to provide ease of using business features to engage all sorts of users. Quality assurance of mobile applications ensures the efficiency, user experience, performance and robustness are meeting the user expectations.</p><p>Mobile testing is always complex when compared to the web UI testing. Mobile is used across different regions with more number of users accessing it widely. So it needs through testing especially on the applications that are downloaded from both IOS and Android stores. The Mobile application function has different types:</p><ul><li>Native Application (It is specific to Android or IOS).</li><li>Hybrid Application (It can be accessed by both Android and IOS).</li><li>Web Application (These are accessed through the native mobile browsers).</li></ul><p>Both functional and non-functional testing has to be done for all the mobile applications. The functional testing involves, Critical business flows, UI enhancements, backend verifications and cross browser testing. The non — functional testing involves endurance or performance testing to test and validate the Stability of the application. A complete security and penetration testing should be certified before launching.</p><p>Mobile automation testing can be done with Appium framework and the web application can be done with Selenium or Cypress frameworks. It is always better to do testing on real devices than using simulators for certification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/0*SIwgWy5GgioFhoHU" /></figure><p>Usually functional testing covers the application launch, verify key business flows and the usability testing covers the design and layout verification. The other important testing is compatibility testing. This verifies the application on different mobile devices with different memory and processor. Also test both on Android and IOS platforms. For the web versions, it has to be verified on different browsers like Chrome, Safari, Firefox.</p><p>Performance testing has to be verified for Device, Network and Server performance.This type of testing validates the request and response time between the network and the server. We should also validate the battery consumption and Memory consumption test, this could be one of the reasons for the slowness of the application. For testing performance manually try using a light version of phones or some old model. Such devices would more obviously show all performance issues.</p><h4>Checklist for mobile application testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/0*nnfiw7bsOM4Ip51H" /></figure><p>Mobile testing also has a big dependency on the hardware. It is important to test compatibility in different devices, screen size, resolutions, OS (and browsers for web applications). Of course it is impossible to cover all phones/ tablets models as well as many Android and iOS versions. We advise you to investigate the market usage in the country where your application would be used or analyse Google Analytics data of your application and cover the most popular.</p><p>Mobile type of devices foncees having different types of Internet connection. Please keep in mind testing major use cases with Wi-Fi as well as sim card mobile data connection. Cellular internet connection is commonly forgotten during mobile testing. Usually QAs have Wi-Fi only models of IPads to save costs of test devices and experience lack of sim cards for the testing. We were making the same mistakes and skipping quite severe bugs specific to cellular internet connection.</p><p>While testing on mobile we advice to keep in mind:</p><ul><li>Interface for different screen orientation (portrait and landscape).</li><li>Making/Receiving/Rejecting voice calls while the app is running.</li><li>Sending a mobile app to background (and resuming it).</li><li>Keyboard for edit Fields as well as checking responsiveness of the drop-downs.</li></ul><h3>Big Screens</h3><h3>Set-top Boxes</h3><p>Set-top Box is a device, which displays on connected output TV content. As input it can use cable television or IP TV signal. Thanks to STB the TV content can be shown on TV devices or even monitors.</p><p>While we talk about testing on Set-top boxes, we can categorise into 2 types of testing. One the extensive testing done on the set-top box device itself. This testing basically ensures the video &amp; audio quality, tuner quality and also other interface testing. The other type of testing is done on the application that is deployed on the set-top boxes, that includes both middleware and the UI that we see on the TV screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jy406H_ApnHB1_rT" /></figure><p>Most of the Setup box UI testing is done manually and the stress or endurance testing is done by automation. The automation scripts are executed to the set-top — box and the logs are captured to validate the crash failures. This type of testing needs a lot of creative &amp; out of the box scenarios to make sure the application works properly. Here are the few test scenarios that have to be focussed on the below functionalities.</p><ul><li>Electronic Program Guide — Test Reminders, Check for program time and date</li><li>Digital Video Recorder (DVR) — Check for the recording capacity, rewind, play recording etc..</li><li>Channel list — Look for the channel list and scroll for navigation</li><li>Search list — Give multiple searches and check for the functionality based on program, movie, artist, etc..</li><li>Video on Demand (VOD) — Check for the list of Content available, play stop, rewind etc..</li></ul><p>While testing applications for STBs it is important to keep in mind testing all possible Internet connections (throw LAN or Wi-Fi). Also covering use cases with low speed or not stable Internet connection would be very helpful.</p><p>We advise you to include into the STB test approach installation testing. We would compare this part with the login module. If the user is not able to get updates on the hardware, he/she can not enjoy even last added features.</p><p>While testing on STB, it is important to keep in mind that every touch screen has hard and soft keys. The soft keys are part of the UI and they can be pressed by making the button focused and pressing on it by Ok (or similar button on the remote control). The hard keys are keys on remote control. The user can press back, exit, play, pause, record buttons on UI or directly on remote control. As QA you need to cover all hard keys and all soft keys on every screen.</p><p>If we would compare STB with other apps, it is important to include a test scope specific to firmware features (like peering of remote control, connecting storage devices, supporting several versions of remote controls or switching between different languages).</p><h3>Other Big Screens</h3><p>By the big screen applications we mean applications, which can be installed on Big Screen devices, which are usually used in living rooms. It can be Apple TV, Fire TV sticks/ boxes/ cubes, Xboxes, different smart TVs with Android TV (like some models of Sony or Philips) or OS created by TV vendors like Web OS (new models of LG TVs), Tizen and Orsay (Samsung TVs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RnDuqBBg7dcNpKJx" /></figure><p>See more extended list of vendors and OS in section “Smart TV platforms utilized by vendors” in the <a href="https://en.wikipedia.org/wiki/List_of_smart_TV_platforms">Wikipedia article</a>.</p><p>Those big screens can use native, hybrid or web applications. However if you are thinking about the test automation on big screen apps, consider the <a href="https://suite.st/docs/devices/">Suite.ST</a> framework. It allows us to launch automated tests on real devices.</p><p>Like in STB testing, it is important to cover with tests LAN and Wi-Fi Internet connection, soft and hard keys as well as installation testing. Compared to STB those devices have the complexity level of different hardware and OS combinations.</p><h3>Casting</h3><h3>Google Cast</h3><p>Google Cast is a technology for playing Internet streamed audio/video content on compatible TV/monitor or audio systems. The user needs a sender and receiver compatible device for casting.</p><p>Sender is a place where the user controls the playback. It can be mobile/ web apps which support Google Cast feature. Mirroring the screen from Chrome desktop browser or Android mobile phones is also possible.</p><p>Receiver is a place where audio/video stream is played. The chrome cast receiver is commonly built into TVs with Android TV operating system, devices like Google Nest, some sound bars and speakers. Chrome cast devices can be also used as receivers. They are designed as small dongles that are powered by connecting the device to an external power adapter or USB. Video-capable Chrome casts plug into the HDMI port of motor or TV, while the audio-only model outputs sound through audio jack. There are many different models of the chrome casts: 1st Generation, 2nd Generation, Audio (for use with audio streaming apps), Ultra (supports 4k resolution), 3rd Generation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*Ts41ZqSEgtfy4mGtSAZnFQ.png" /></figure><p>While testing the Google Cast feature we advise using different test levels: component testing for testing separately senders and receiver apps and integration testing to check flow of casting. If casting is a new feature to you, it is worth checking <a href="https://developers.google.com/cast/docs/testing">test cases prepared by Google</a>. Those 2 files suggest the essential scenarios of the sender, different types of receivers, multi-sender scenarios, playback or establishing connection.</p><p>For a successful integration testing approach, keep in mind different parameters which impact on casting and cover different combinations. Classical examples would be different receiver and sender devices and quality of stream. If you start mixing those parameters, your test coverage would be much bigger. How the scope may look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/0*POkzkGjTc17YBpqW" /></figure><p>You can enlarge your approach with DRM or non DRM content, different types of players, different streaming protocols (<a href="https://www.dacast.com/blog/streaming-protocols/">more about them</a>). Knowing the app architecture and talking to developers would help to define those parameters.</p><p>By including more parameters you may face large complexity and would not be able to manually design peers. There are many pairwise tools, which can mix combinations in smart algorithms (<a href="https://jaccz.github.io/pairwise/tools.html">list</a>). We offer <a href="http://testcover.com/pub/eqpt.php">Test cover</a>, as it supports constraints when some combinations of parameters are not possible.</p><h3>AirPlay</h3><p>AirPlay is a technology designed by Apple that allows wireless audio/video streaming as well as screen mirroring between the compatible devices. Like in Google Cast the AirPlay uses the concept of sender (IPhones, IPads) and receiver (Apple TV).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_a0_AeBeE_ikh5jU" /></figure><p>For that reason it is worth following the same test approach to apps supporting AirPlay as for Google cast: component testing of each app separately and integration testing with different combinations of parameters.</p><p>Testing mobile, STB, big screen and casting applications has not so many differences compared to web applications. Of course such applications have bigger dependency on hardware and some new use cases related to specify how the applications are being used. If you always wanted to try testing them, switching would be very easy going. Just do it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a206010d0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quality-matters/test-strategy-in-mobile-and-big-screen-testing-a206010d0d">Test Strategy in Mobile and Big Screen Testing</a> was originally published in <a href="https://medium.com/quality-matters">Quality Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Importance of Exploratory Testing]]></title>
            <link>https://medium.com/quality-matters/importance-of-exploratory-testing-3f02e34dc0c3?source=rss----c5cc384cc19d---4</link>
            <guid isPermaLink="false">https://medium.com/p/3f02e34dc0c3</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[exploration]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Mariia Hutsuk]]></dc:creator>
            <pubDate>Wed, 21 Oct 2020 16:11:11 GMT</pubDate>
            <atom:updated>2020-10-21T16:28:36.936Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>This story is co-authored together with </em><a href="https://medium.com/u/827cc9350bfb?source=post_page-----f55fc40439c6--------------------------------"><em>Sivamoorthy Bose</em></a></p><p>Exploratory testing is an approach to testing whereby the testers dynamically design and execute tests based on their knowledge, exploration of the test item and the results of previous tests (<a href="https://glossary.istqb.org/en/search/exploratory%20testing">according to ISTQB Glossary</a>).</p><p>Exploratory testing is commonly confused with ad-hoc testing, which is performed on demand without scripted test cases, or monkey testing, which is done with random user actions. Exploratory testing is learning a product with small experiments and adapting new experiments during the testing session. Such kind of testing perfectly fits Agile with a similar mindset as Agile experiment.</p><h3>Benefits of Exploratory Testing</h3><ol><li><strong>Exploratory testing catches more defects than automated.</strong></li></ol><p>Let’s see some of the metrics that show why exploratory testing is so important.</p><ul><li>33 % of complex bugs in an application are found through exploratory testing.</li><li>29% of the UI Bugs are found through exploratory testing than automated script testing.</li><li>Exploratory testing identifies 11% overall defects than automated script testing.</li></ul><p>Source : <a href="https://www.perforce.com/blog/alm/what-is-exploratory-testing">https://www.perforce.com/blog/alm/what-is-exploratory-testing</a></p><p>Exploratory testing helps to deliver a more quality product to the market with more test coverage.</p><p>2. <strong>Exploratory Testing Helps to Share Domain Knowledge</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/0*p1CXqUcCjZcNX1gN" /></figure><p>Exploratory testing can be performed in pairs using peer programming principles. It assumes 2 roles: of driver and navigator. Driver is a person at the wheel, this person should focus on the application while he/she is performing actions and ask questions if they occur. The navigator is in an observer position and tells direction of further checks and makes notes of steps or findings. Those roles can be changed from time to time. This approach can not just help to find bugs, but also explore products and share knowledge of some features within pear.</p><p>3. <strong>Exploratory Testing Helps to Switch Focus of Attention</strong></p><p>Human attention is an interesting mechanism. When we focus on something specific we don’t notice everything else unfocused. Even multitasking people don’t have more than one focus, they just switch attention very fast. Look at this video to see in-attentional blindness in action:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_bnnmWYI0lM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_bnnmWYI0lM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_bnnmWYI0lM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b4bce84340a2e15c2217039f560a00c6/href">https://medium.com/media/b4bce84340a2e15c2217039f560a00c6/href</a></iframe><p>Confirmation bias is one more attentional tendency, which impacts testing. It is a tendency to pay attention to facts, which prove the personal beliefs. Let me share one of our experiences that we faced such bias during testing. We had a requirement of an expected colour scheme for the app describing first and secondary colour and where they should be shown. We almost skipped an important visual issue: write text was written on a light yellow button.</p><p>One of key benefits of exploratory testing is that it helps to deal with cognitive biases and focus on different perspectives in our application.</p><h3>How to Transform to Exploratory Testing Mindset</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/0*oQhDuMQUgBWbZQDi" /></figure><p>This is an era, the entire QE industry is moving towards shift left testing and establishes QE process. As we focus on functional and automation testing but still we find gaps in test coverage. Every tester should have the mindset to do exploratory testing at least once in a week. There is always limitation in our automation scripts and it has boundaries. Automation regression testing alone cannot find bugs that cover all the scenarios. Scripted testing can only verify what is in the script, catching only conditions that are expected. Such tests can be a fine net that catches any bugs that try to get through it, but how do we know that the net covers all those scenarios?</p><p>Exploratory testing seeks to test the boundaries of the net, finding new behaviours that aren’t in any of the scripts.</p><p>Source : <a href="https://martinfowler.com/bliki/ExploratoryTesting.html">https://martinfowler.com/bliki/ExploratoryTesting.html</a></p><h3>What attributes QA should have?</h3><p><strong>Inquiring</strong> — Exploratory testing doesn’t pre-determine what’s to be tested or how, so great exploratory testers are inquisitive and interested. They want to find out everything. They want to know what’s behind this door (or button) or and what’s hiding in this box (or feature). They need to be driven to learn more since they’re on their own when it comes to <a href="https://test.io/website-testing/">checking the different parts of the website</a> or application and investigating its nooks and crannies.</p><p><strong>Flexible</strong> — Great exploratory testers are competent test designers who can roll with the punches: if an investigation of a specific part of the software turns up an error, they need to be able to improvise new tests that look for related problems and issues. An exploratory tester who is good at coming up with impromptu additional tests can also determine the scope of a bug, or at least circumscribe the impact of it, which makes the task of fixing it easier for the developer.</p><p><strong>Observant</strong> — Inquisitiveness isn’t enough on its own. Exploratory testers should not only be curious, but also able to notice any aberrations and document them. An excellent exploratory test requires the testers to observe settings, environmental factors, and internal mindsets as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/0*3NDa1eR6t21vvBgP" /></figure><p><strong>Holistic</strong> — Exploratory testing needs to consider and record anything that may influence the testing. This could range from factors such as: wifi versus cellular, signal strength, battery level, or even ambient noise. The great exploratory tester embraces the need for additional investigation and fully considers all paths that should be investigated instead of settling for one scripted solution.</p><p><strong>Excellent Communicator </strong>— Someone can be intelligent and inquisitive and awesome at finding defects, but it does little good if they can’t communicate their test findings to the developers. Without a separate test designer sitting down with the product manager to pre-determine individual testing steps and expected outcomes, testers are responsible for explaining the idea behind a given test, the circumstances surrounding it, and then the outcomes that result.</p><p>Source : <a href="https://test.io/exploratory-testing/">https://test.io/exploratory-testing/</a></p><h3>How to Organise Exploratory Testing Session</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/0*zHQ5UyvoyG2Hj4ZL" /></figure><p>Even exploratory testing does not need scripted test cases, it needs some procedure. We recommend reserve time to perform exploratory testing on a regular basis. Session based approach is the best way to conduct this type of testing.</p><p><strong>Prioritise the Bugs</strong></p><p>During testing, each tester knows the cluster that has the most number of bugs in an application. Prioritise those clusters and start doing exploratory testing on those cluster code bases.</p><p><strong>Include Exploratory Testing in the Test plan</strong></p><p>When you create a master test plan, include exploratory testing as part of the plan. Have at least 1 tester to do this activity on a weekly basis.</p><ul><li>Include Module or feature to be focussed.</li><li>Include What all the tool, technique, configuration.</li></ul><p><strong>Create a Time Bound for Testing</strong></p><p>Have a specific time frame to do exploratory testing for each release and also validate those results with the development team and address them on time.</p><p><strong>Testing Charters</strong></p><p>There is a simple template suggested by Elisabeth Hendrickson in the <a href="https://www.amazon.com/Explore-Increase-Confidence-Exploratory-Testing/dp/1937785025">book “Explore It!”</a>, which can be used for planning the scope of exploratory testing sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/0*aH21xqBV_yp4M7-Z" /></figure><ul><li>Target: where will you explore? (feature, module).</li><li>Resources: what should you use? (tool, technique, configuration).</li><li>Information: what are you hoping to find?</li></ul><p>There is a nice example provided by Elisabeth, which we especially like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/0*9v2plTCzPkk9PkEM" /></figure><p><strong>Testing Tours</strong></p><p>Testing Tours is an amazing alternative to Charters. In the book “<a href="https://www.amazon.com/Exploratory-Software-Testing-Tricks-Techniques/dp/0321636414">Exploratory Software Testing</a>” James A. Whittaker suggests the concept of testing tours. The idea is to compare software with a city. QA is supposed to explore the city from different perspectives. You can select the existing tour or invent your own.</p><p>We suggest trying the garbage collector’s tour. In the real world the garbage collector spends a short time at each house, picking up the garbage. He has one specific task to do methodologically for each house. It can be used to test every menu item or all validation/ error messages, modal windows.</p><p><strong>Personas</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/140/0*TtcnfvI4OxSh35DF" /></figure><p>You may notice that you or your QA colleagues use the argument “As a user I expect….”. In many cases it is a valid expression and the QA person is really a user of the system being tested. QAs also have bank accounts, book flights or order food. But in many cases we are not users of the system, which we test. We can test incident management systems for oil production and most of us never worked on such dangerous productions. That is why it is important to know who are real end users and be flexible enough to switch the mindset. Persona enables QAs to test applications with fresh perspective.</p><p>You can define persona like here:</p><p>Janet is a 67 years old pensioner, who has a dog. Modern technologies are not important to her therefore she has a slow Wi-Fi connection at home, light version of Android tablet and no notebook. Test ordering dog accessories as Janet, who has plenty of free time and patience with her slow connection.</p><p>When QA assumes Janet’s persona, she would start using applications in a special way, not like ordinary. Her technical set-up may cause that long registration form not saved and more steps with saving data could be helpful. She may face issues with website responsiveness on the mobile device or can be confused by lack of loaders.</p><h3><strong>Conclusion</strong></h3><p>As we move on towards shift left testing and identify the critical bugs as early as possible then exploratory testing should be part of the testing life cycle. This also helps to identify the gaps in the test and automation coverage. Exploratory testing is nothing but playing around the application with no boundaries and rules. Lets enjoy doing it more often!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f02e34dc0c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quality-matters/importance-of-exploratory-testing-3f02e34dc0c3">Importance of Exploratory Testing</a> was originally published in <a href="https://medium.com/quality-matters">Quality Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Have QA Managers Transformed to Agile?]]></title>
            <link>https://medium.com/quality-matters/have-qa-managers-transformed-to-agile-8030df633b86?source=rss----c5cc384cc19d---4</link>
            <guid isPermaLink="false">https://medium.com/p/8030df633b86</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[dev]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[transformation]]></category>
            <dc:creator><![CDATA[Sivamoorthy Bose]]></dc:creator>
            <pubDate>Wed, 12 Aug 2020 15:03:54 GMT</pubDate>
            <atom:updated>2020-08-12T15:03:54.825Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>This article is co-authored together with <a href="https://medium.com/u/dd1e84cb14ab">Mariia Hutsuk</a></li></ul><p>In recent years Agile has become more and more popular in various organizations. As quality people in leadership, we faced a dilemma if our positions are demanding and would stay so in a couple of years more. Although the traditional management roles are gone, managers still have their place but their responsibilities and scope may look quite different.</p><p>In this article, we would explain how we transformed our duties to bring value and don’t kill Agile in our teams.</p><p>As Stephen Janaway cites in his blog post on “<a href="https://stephenjanaway.co.uk/stephenjanaway/management/end-road-test-managers/">The End of Road for Test Managers?</a>”:</p><p>“Being a Test Manager in an Agile environment can be isolating at times, particularly when the department is big, and the number of agile teams is large. It requires an ability to balance a lot of information, priorities, and tasks, across a number of areas. Stakeholder management and influence become key. Context switching comes as standard”</p><h3>How should a QA Manager’s role transform in Agile?</h3><h3>DevOps becomes DevTestOps</h3><p><a href="https://agilemanifesto.org/">The Agile manifesto</a> appeared almost 20 years ago in 2001. Those statements made a real revolution in the IT field. Back then there were no technical possibilities on how to implement some of its principles like the following:</p><p>“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”</p><p>Luckily now we have enough technical DevOps ways to apply ideas of fast and frequent releases to reality.</p><p>QA Manager should build necessary continuous testing processes part of the delivery pipeline. There is no need anymore to plan 1–2 weeks iterations of testing to launch some features. Some testing activities can start even on the developer’s machine and first bugs can be written on a piece of paper. Some feature testing can be performed even on production.</p><p>You can build a new process with your team collaboratively. As a start, you just need to visualize your release activities. We suggest choosing your own way of doing it. It can be drawing activities with stickers and physical boards, playing the <a href="https://www.praqma.com/stories/pipeline-card-game/">Pipeline game</a> of Emily Bache, or even using some online facilitation tools like Jamboard, Miro, or Mural. This simple exercise would help you to identify issues and their solutions as a team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IOijUIrBS44uM4e0" /></figure><p>How the release pipeline can look thanks to cards of the Pipeline game.</p><p><strong>Servant Leadership over being a Boss</strong></p><p>Modern Agile concepts like T-shaped specialists, servant leadership modified not just QA leadership roles, but leadership roles in general. There is no need of having a Boss in a team, who assigns tasks and communicates with everyone.</p><p>Look how Jason Yip is describing <a href="https://medium.com/@jchyip/why-t-shaped-people-e8706198e437">collaboration of T-shaped people</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/0*LSLFnCzZW2bt6fNl" /></figure><p>Being a servant leader, you need to empower your subordinates to take independent decisions and build an environment of psychological safety. You can not know everything, by trusting and relying on your team you would receive a much better outcome. Her you have a youtube video about what servant leadership mean</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOqmdLcyES_Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOqmdLcyES_Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOqmdLcyES_Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/043cb345a650c43a1a4f6ac3f9707bca/href">https://medium.com/media/043cb345a650c43a1a4f6ac3f9707bca/href</a></iframe><p><strong>Build a team of T-shaped Specialists</strong></p><p>Each of us has some skills. Some people are specialists in one field, they are called I- specialists. They are experts in one duty and can not perform others. Some people are generalists and they have much expertise, but no deep knowledge in any field.</p><p>By being in a QA leadership role, you can focus on developing more skills for I-specialists and focusing on some deep-dive learning for all generalists.</p><p>You might have noticed that Jason Yip on a previous image painted just 3 T-shaped specialists and 6 I-shaped. It really reflects the reality. You would need less T-shaped people to execute the same scope of tasks and there would be no need for a boss mediator.</p><p><strong>Testing Coach / Facilitator</strong></p><p><a href="http://katrinatester.blogspot.com/2014/04/test-manager-in-agile.html">Katrina Clokie in her blog “Test Manager in Agile”</a> mentions, the Test Manager role as evolving to a higher-level position that includes:</p><ol><li>Facilitation of inter-team communication across many agile projects within an organization</li></ol><p>2. Presenting an aggregate view of testing utilization to high-level management</p><p>3. Personal support, mentoring, and professional development for testers</p><p>4. Being an escalation point for testers</p><p>5. Budgeting or forecasting for testing as a service dependent on organizational process</p><p><strong>Forming End-End System Integrated Team</strong></p><p>SAFE(Scaled Agile) has multiple Agile teams, each team is usually focused on their own feature and they will develop, test, and deliver an incremental working functionality at the end of each iteration. But the real problem arises when no one sees the big picture on how all team deliverables are integrated into one complete product.</p><p>QA manager can lead an E2E system test team that consists of a few testers who would test the E2E features that need to be tested beyond teams. This ensures that the integration between teams works well as a whole product. QA managers can provide insights into the overall product quality based on their test results and this is one major responsibility.</p><p>This team should also test the Non-functional testing like the Load test, Stress test, and Dynamic securing testing like the pen test.</p><p>This team should have testers with multiple skill knowledge on tools like Jmeter, selenium, Zap, etc.. Individual agile teams will not focus on non-functional testing, so the QA manager can take the opportunity of building this team to focus on all those areas.</p><p><strong>Form Test Center of Excellence</strong></p><ol><li>Managers can define a test process that is common to all the agile teams that work across.</li><li>Standardized test framework according to UI, API, and microservice testing, unless there is a need for a change in framework.</li><li>Managers can enforce DOD manifesto into agile teams. DOD mostly depends on testers feedback and demo.</li><li>For more details on DOD please refer <a href="https://medium.com/quality-matters/does-your-agile-team-follows-definition-of-done-ecc9e58b5ebb">Siva’s article</a></li><li>Set Up a good signoff process from testers to Scrum Masters.</li><li>Make sure testers are not testing on Adhoc request, they should test only on the user stories planned or modified.</li></ol><p><strong>Set the Quality Metrics</strong></p><p>The business always depends on good quality metrics. These metrics build confidence in the product that’s been delivered in Agile. Managers can take the role of defining and setting the right KPIs. Here are some of the KPIs that can be defined to measure the quality of the Product.</p><ol><li>Track Automation Velocity</li><li>Test Requirement Coverage</li><li>Defect Trend — Open, closed</li><li>Regression execution Status</li><li>Automation Coverage for User Stories</li></ol><h3>Future of QA Manager’s positions on the market</h3><p>The current market has a lot of leadership opportunities for Quality people and we assume that they would stay in upcoming years. Here are a few of those positions that have similar roles and responsibilities that every QA manager can consider.</p><p><strong>QA Manager</strong></p><p>In recent years the demand for QA Team Lead position with functional management duties has changed as in most cases cross-functional development teams have solo QAs.</p><p>However, the QA Manager roles are quite often open. Depending on organizational values it may include line management or not. Such specialists usually perform duties described in this article.</p><p><strong>Quality Coach</strong></p><p>Agile teams usually have big autonomy and are empowered to develop/test/deliver by their own resources. It is impossible to impact such teams with power. Therefore the appearance of the Quality Coach role is very natural.</p><p>Quality coaches stop testing by himself/herself and influence without power on others on questions regarding quality. This sounds quite complex. In fact it is not, it is fun. Quality Coaches should have a lot of patience and persistence. People would start trusting after the first successes and would be open to more brave changes. Quality Coaching is about fixing not software, but mindsets of people, who create software.</p><p><strong>Product Manager</strong></p><p>Product managers provide the deep product expertise needed to lead the organization and make strategic product decisions. They often analyze the market and competitive conditions, laying out a product vision that is differentiated and delivers unique value based on customer demands. The role spans many activities from strategic to tactical and provides important cross-functional leadership — most notably between engineering, marketing, sales, and support teams.</p><p><strong>Engineering Manager</strong></p><p>Some Quality people in leadership positions may find attractive an Engineering Management career path.</p><p>How do you measure the software quality? You can count the amount of known critical bugs or track lead time for changes, deployment frequency, time to restore service, change failure rate to understand the maturity of delivery processes. Read more on <a href="https://stelligent.com/2018/12/21/measuring-devops-success-with-four-key-metrics/">Paul Duvall’s article</a> about matrics taken from “<a href="https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339">Accelerate</a>” book by Nicole Forsgren, Jez Humble, Gene Kim. If you measure quality differently, you can easily switch the focus and the mindset to manage the development considering testing as part of it.</p><p><strong>To Conclude</strong></p><p>Overall a QA Manager should stay abreast of new developments in the QA domain, evaluate new tools, and learn new methods. They should also constantly improve on those by defining activities, setting priorities, and balancing resources at the group level. They can make sure the teams don’t fall over each other, and that everyone is talking to the right people</p><p><strong>Useful links for reference:</strong></p><ol><li><a href="http://katrinatester.blogspot.com/2014/04/test-manager-in-agile.html">Test Manager in Agile by Katrina Clokie</a></li><li><a href="https://stephenjanaway.co.uk/stephenjanaway/management/end-road-test-managers/">The End of the Road for Test Managers? by Stephen Janaway</a></li><li><a href="https://medium.com/helpsystems-armenia-writes/a-qa-managers-role-in-an-agile-organization-d0906a3fe7f8">A QA Manager’s Role in an Agile Organization</a></li><li><a href="https://medium.com/quality-matters/does-your-agile-team-follows-definition-of-done-ecc9e58b5ebb">Does your Agile team follows — Definition of Done? By Sivamoorthy Bose</a></li><li><a href="https://medium.com/@jchyip/why-t-shaped-people-e8706198e437">Why T-shaped people? by Jason Yip</a></li><li><a href="https://www.praqma.com/stories/pipeline-card-game/">Pipeline — The Game that Delivers!</a></li><li><a href="https://stelligent.com/2018/12/21/measuring-devops-success-with-four-key-metrics/">Measuring DevOps Success with Four Key Metrics by Paul Duvall</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8030df633b86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quality-matters/have-qa-managers-transformed-to-agile-8030df633b86">Have QA Managers Transformed to Agile?</a> was originally published in <a href="https://medium.com/quality-matters">Quality Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does your Agile team follows — Definition of Done?]]></title>
            <link>https://medium.com/quality-matters/does-your-agile-team-follows-definition-of-done-ecc9e58b5ebb?source=rss----c5cc384cc19d---4</link>
            <guid isPermaLink="false">https://medium.com/p/ecc9e58b5ebb</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[safe]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Sivamoorthy Bose]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 20:04:52 GMT</pubDate>
            <atom:updated>2020-07-08T20:04:52.423Z</atom:updated>
            <content:encoded><![CDATA[<h3>Does your Agile team follows — Definition of Done?</h3><p>DOD is a very common discussion for those who work on agile teams. Not all teams follows the exact criteria for Definition of Done. DOD vary from team to team but it should be consistent within the team. A user story gets ready for release only if that feature is considered as “Done”. It is important to identify a DOD that works for your team and your business needs and ensure everyone in the team understands the DOD manifesto. As a team matures, we expect it to adapt its DOD to ensure higher quality.</p><p>Here are some of the ways, where we can enforce DOD across teams successfully.</p><p><strong>· Use a clear DOD Manifesto or Checklist for user stories that are checked against.</strong></p><p><strong>· Scrum Masters and Product Owners have to make these Checklist as Mandate.</strong></p><p><strong>· Ensure the increment shipped at the end of the sprint has high quality and that the quality is well understood by all involved.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AOB0wpg-v9oRCQ84RqYGww.png" /><figcaption>Stages for DOD</figcaption></figure><p>Following up the manifesto is very much important and each organization can visualize their strategy and they can tweek it accordingly.</p><p>The below manifesto covered almost all the key activities that we follow up in the agile teams. I have taken this image from Naren’s scratch pad and would like to give credits for him too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mK0_SELJ152Zrz0-.png" /><figcaption>@ Source from Naren’s Scratch Pad.</figcaption></figure><p>As we have Epic, Features and Stories, DOD can be different for each of these categories and here are some examples for each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LmCQPnmwbxdKb1N3jfNd-w.png" /></figure><p>All these will helps us to deliver valuable product to our customers and meet our business goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecc9e58b5ebb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quality-matters/does-your-agile-team-follows-definition-of-done-ecc9e58b5ebb">Does your Agile team follows — Definition of Done?</a> was originally published in <a href="https://medium.com/quality-matters">Quality Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Determining The Priority for Test Automation]]></title>
            <link>https://medium.com/quality-matters/determining-the-priority-for-test-automation-f55fc40439c6?source=rss----c5cc384cc19d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f55fc40439c6</guid>
            <category><![CDATA[ui-testing]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[Mariia Hutsuk]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 15:33:59 GMT</pubDate>
            <atom:updated>2020-07-14T16:09:38.538Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This story is co-authored together with <a href="https://medium.com/u/827cc9350bfb">Sivamoorthy Bose</a></blockquote><h3>Determining The Priority for Test Automation</h3><p>As a First Step of test automation, most of them determine the need for an automation tool but before that identification of priority and feasibility of test cases is very important. Every aspect should be considered while analyzing the feasibility. It is also essential to perform a feasibility analysis on the manual test case pack that allows automation engineers to design the test scripts.</p><p>In this particular stage, the following questions should always be asked.</p><ol><li>Which modules of the applications can be automated and which cannot?</li><li>Which tests can be automated and how do you automate them?</li><li>Factors like cost, team size, and expertise should also be considered.</li></ol><p><strong>What to automate? What to explore?</strong></p><p>Many software systems are quite complex. Sometimes we don’t understand or don’t have data regarding how the feature is being used by the end-users like it is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/0*y7KQtE0k_XwhdB_U" /></figure><p>The test automation uses the principle of checking. It addresses the question “Does the system do what it is supposed to do?” It can bring the biggest value when it covers known knowns. When you know the clear use cases of a feature and you have data proving it (from google analytics/ AB testing or other researchers) it is the best scope to be automated.</p><p>What about other risks and system vulnerabilities that we are not aware of? This can not be automated, it should be discovered first by human-centric testing.</p><p>What about unknown knowns or known unknowns? Those areas should be researched first by humans. If we would “delegate to robots” those areas the tests can be useless. No one can use this feature or we could have a wrong hypothesis regarding how it is being used.</p><p>Lisa Crispin and Janet Gregory also advise to leave risks and vulnerabilities on their “How to Implement Testing and Agile in a Company” webinar (watch <a href="https://www.agilealliance.org/resources/videos/how-to-implement-testing-and-agile-in-a-company/">recording</a>). They also introduce the term “human-centric testing” instead of manual testing to value human effort of mindful product discovery. We also share this mindset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/0*37NNpeqTc7QQdn_7" /></figure><p>However, should we really automate all known knowns? Of course no, let’s dive into this deeply.</p><p><strong>What kind of tests should NOT be automated?</strong></p><ul><li>Tests that need to be executed only once.</li><li>Tests that need to be verified with human discretion.</li><li>Tests that are very quick to execute.</li><li>It’s not always suggestible to automate tests during usability tests.</li><li>Test that takes more time in automating than in executing manually.</li></ul><p><strong>What Test Cases to Automate :</strong></p><p><strong>Business Critical Flows :</strong></p><p>The test cases or functions that are mostly used by the end-users in PRODUCTION. We have to make sure these cases are automated and tested thoroughly in regression.</p><p><strong>High Priority Progression test cases:</strong></p><p>Automating Critical or high priority progression test cases helps to cover the majority of code changes.</p><p><strong>Test Cases to test with Large Data :</strong></p><p>Any test cases that need large data input has to be automated, which would save huge ROI when compared to Manual effort.</p><p><strong>Smoke or Sanity test cases:</strong></p><p>The major test cases that have to be tested for every build has to be automated and these tests should be executed daily.</p><p><strong>Complex Cases :</strong></p><p>Automating complex test cases is almost a rule. Again, you do want to be on the safe side and to save your time when it comes to complexity. If you have some routine and long to execute tests, where humans can make mistakes, automate it as well. Test automation is a tool that helps to speed-up the testing activities.</p><p><strong>Test Cases to be executed on Cross browsers:</strong></p><p>Automation can be done for those test cases that have to be tested on multi browsers, typically browser capability testing.</p><p><strong>Automatable Cases:</strong></p><p>Validate test cases that can be automatable, look for automation feasibility with respect to the cost of automation, complexity, and reusability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/0*37_j_FD9LuoENpPI" /></figure><p><strong>Maintain Smaller Test Suite :</strong></p><p>Maintaining a smaller automated test suite is always important, since regression testing often demands that the test suite is executed with every build and for every change made to the project. Splitting the test suite into smaller chunks is a viable option to reduce execution time. Creating Jenkins jobs for these smaller chunk automated suites helps to integrate into the CI/CD pipeline.</p><p><strong>Automate tests with broader Test Coverage :</strong></p><p>By using a minimization technique, identify tests that cover the broadest spectrum of faults, prioritize the test cases that can be considered for automation. This would help in faster execution with broader test coverage.</p><p><strong>How to start automation? Visualize a Test Strategy as a Team!</strong></p><p>We shared some principles of selecting the automation scope from our experience. However, your project is unique and your team knows best what to automate. Even if you already have some automated steps, it is always useful to take a step back and think about priorities and on what priorities to focus on next. Using visual models would help you to get the whole team involved.</p><p><strong>Test Automation Pyramid:</strong></p><p>One of the well-known tools is the test automation pyramid. Usually, it is divided into 3 sections of unit, API and integration as well as E2E tests. Read about it more on <a href="https://medium.com/@sivamoorthy.bose/is-test-pyramid-still-a-challenge-1f8ed97c2f2b">Siva’s blog</a>. Discuss with your team what tests you can “push lower”.</p><p><strong>Testing Quadrants:</strong></p><p>One more thinking and conversational tool is testing quadrants. It can help to understand what types of testing are needed and in which order they should be performed.</p><p>The key idea is to define 4 quadrants depending if the testing type is business/technology facing or if it is guiding development/critique of the product. After filling collaboratively the quadrants the team can define the priority order depending on the project needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/0*pxRYbpjAgBIiXAQb" /></figure><p>Read more about the tool on <a href="https://lisacrispin.com/2011/11/08/using-the-agile-testing-quadrants/">Lisa Cryspin’s blog</a> (image is taken from there).</p><p>Test automation is not a goal, it is a tool to achieve the goals of your team. A smart definition of scope to be automated and test strategy can help you to become more efficient and manage better the balance between its value and maintenance cost. Visualizing your thoughts in a team is also extremely helpful. Try it out, you would get a lot of value!</p><p><strong>Useful references:</strong></p><ul><li><a href="https://medium.com/datadriveninvestor/known-knowns-unknown-knowns-and-unknown-unknowns-b35013fb350d">Known Knowns, Unknown Knowns, and Unknown Unknowns</a></li><li><a href="https://www.agilealliance.org/resources/videos/how-to-implement-testing-and-agile-in-a-company/">How to Implement Testing and Agile in a Company webinar</a></li><li><a href="https://medium.com/@sivamoorthy.bose/is-test-pyramid-still-a-challenge-1f8ed97c2f2b">Is Test Pyramid still a Challenge?</a></li><li><a href="https://lisacrispin.com/2011/11/08/using-the-agile-testing-quadrants/">Using the Agile Testing Quadrants</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f55fc40439c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quality-matters/determining-the-priority-for-test-automation-f55fc40439c6">Determining The Priority for Test Automation</a> was originally published in <a href="https://medium.com/quality-matters">Quality Matters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>