<?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 aqua_ALM on Medium]]></title>
        <description><![CDATA[Stories by aqua_ALM on Medium]]></description>
        <link>https://medium.com/@aqua_alm?source=rss-49ad0e8bb3b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*02_o7IHNqHgH-XxiA74RDQ.png</url>
            <title>Stories by aqua_ALM on Medium</title>
            <link>https://medium.com/@aqua_alm?source=rss-49ad0e8bb3b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:52:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aqua_alm/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[What about the test documentation hierarchy?]]></title>
            <link>https://medium.com/@aqua_alm/what-about-the-test-documentation-hierarchy-34d34e113d75?source=rss-49ad0e8bb3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/34d34e113d75</guid>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[aqua_ALM]]></dc:creator>
            <pubDate>Fri, 11 Nov 2022 00:25:28 GMT</pubDate>
            <atom:updated>2022-11-11T00:25:28.389Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWW6pbmPzU6ay8T2stZ00A.jpeg" /></figure><p>Test documentation is a crucial part of the quality assurance process. A well-written test strategy document can help you avoid common pitfalls, and it’s an essential tool for the entire QA team to use to ensure that your product meets the highest standards.</p><p>However, knowing where to start when writing a test strategy document can take time and effort. To help you get started, we’ve created a simple hierarchy of test documentation:</p><p>1)<strong> Test plan</strong>: This is a broad overview of what needs to be tested, who will be doing it, and how long it will take.</p><p>2) <strong>Test case</strong>: A detailed description of what needs to happen during testing. It should include all necessary information about your product so testers can perform their duties correctly.</p><p>3) <strong>Test script</strong>: This is similar to a test case but has been written in such a way as to make it easier for testers and automation engineers alike to understand what they need to do with the software they’re testing (e.g., “click on this button”).</p><p>As the company has been providing a testing tool for agile development since 2013, we have made some suggestions of what a good test strategy may include — you can find them in <a href="https://aqua-cloud.io/testing-strategy/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=share">this article</a>. Thank you for your attention!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34d34e113d75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five common mistakes every QA manager should avoid]]></title>
            <link>https://medium.com/@aqua_alm/five-common-mistakes-every-qa-manager-should-avoid-46ce175602f?source=rss-49ad0e8bb3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/46ce175602f</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[aqua_ALM]]></dc:creator>
            <pubDate>Thu, 03 Nov 2022 23:46:58 GMT</pubDate>
            <atom:updated>2022-11-03T23:46:58.512Z</atom:updated>
            <content:encoded><![CDATA[<p>Once you pass your bar exam, you should have a good idea about quality assurance. However, with every new project, there are always difficulties to overcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2FjTULgAVP-5ybh3vZuC1A.jpeg" /></figure><p><strong>1. Trying to automate everything — despite testing itself</strong></p><p>In an effort to automate testing, some testers forget the true goal of testing — to improve your product through testing. These folks are so focused on automation that they go too far and end up automating everything.</p><p><strong>2. Creating too detailed documentation</strong></p><p>Running the same tests repeatedly on a group of users might be unnecessary and even “dangerous,” mainly because this kind of test is usually the source of overly detailed documentation. And unfortunately, developers have to spend more time diving into all these redundant details. Fortunately, some products help you cut through the extra stuff and focus on what matters.</p><p><strong>3. Forgetting about team spirit</strong></p><p>Even though you may have to deliver criticism, it’s essential to do so diplomatically. Try not to take it personally if the complaint seems directed at you. You need to be professional at work, but it’s also important to remember that you’re dealing with people who are also dealing with their own lives.</p><p><strong>4. Not using all functionality of your </strong><a href="https://aqua-cloud.io/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=share"><strong>bug-tracking software</strong></a></p><p>People only sometimes use the full power of their smartphones; testers may use only a tiny percentage of the functions in their software. For example, they may discuss bugs with their colleagues via instant messaging programs or write them down in Excel spreadsheets and track those bugs in the software.</p><p><strong>5. Bite more than you can chew</strong></p><p>Testers sometimes need to notice how much work they do. They are under enormous pressure to perform tests quickly, but they can only test some things simultaneously. The secret is to break a massive task into small pieces and prioritize them.</p><p>Thank you for reading to the end! If you’ve got some questions, please check our extensive <a href="https://aqua-cloud.io/pitfalls-qa-manager-should-avoid/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=share">blog article</a> dedicated to this topic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46ce175602f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How many solutions for blockchain testing do you know?]]></title>
            <link>https://medium.com/@aqua_alm/how-many-solutions-for-blockchain-testing-do-you-know-147d8fcd5577?source=rss-49ad0e8bb3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/147d8fcd5577</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[aqua_ALM]]></dc:creator>
            <pubDate>Tue, 01 Nov 2022 21:54:45 GMT</pubDate>
            <atom:updated>2022-11-01T21:54:45.832Z</atom:updated>
            <content:encoded><![CDATA[<p>Testing isn’t complete until each aspect has been considered. For blockchain, there are technology-specific user stories that require some extra work before they can be tested. Luckily, the blockchain enthusiasts’ preference for making it all available extends to development and QA solutions as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NIEDiP1JsJbL5MiTGtm_1Q.jpeg" /></figure><p>Just a few suggestions:</p><p><strong>Hyperledger Fabric</strong>: the application blockchain framework with solid support for automated testing, including unit tests that significantly reduce the actual QA effort.. It is specifically designed for bringing business people into development. It provides solid support for automated testing.</p><p><strong>Populus</strong>: is QA-friendly, Python-powered solution for developing Ethereum-based projects. It enables automation and provides a mix of smart contract testing and the pytest framework, which is more universal and widespread.</p><p><strong>The Ethereum Tester</strong>: an alternative product for any blockchain projects, created elsewhere. It comes with its own API and even allows users to mine their own blockchains, if they have a mineable coin.</p><p>To better understand the pros and cons here go beyond developers’ and testers’ convenience as well:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*grZ_nNWZjDwE-TkyvWj9Qg.png" /></figure><p>Blockchain development environments are about combining several <a href="https://aqua-cloud.io/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=share">test automation tools</a> to build and manage a test environment. Remember, your testing is not limited to specialised software.</p><p>If you are interested in other rules and tips for building a successful blockchain testing strategy, please check out our <a href="https://aqua-cloud.io/rules-for-building-a-successful-blockchain-testing-strategy/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=share">blog article dedicated to this topic</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=147d8fcd5577" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What skills should a successful QA team have? Check yours!]]></title>
            <link>https://medium.com/@aqua_alm/what-skills-should-a-successful-qa-team-have-check-yours-73ee0531483c?source=rss-49ad0e8bb3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/73ee0531483c</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[aqua_ALM]]></dc:creator>
            <pubDate>Mon, 31 Oct 2022 00:08:58 GMT</pubDate>
            <atom:updated>2022-10-31T00:08:58.495Z</atom:updated>
            <content:encoded><![CDATA[<p>QA teams should cover the bare minimum: executing manual tests, including interactive, integration, load testing, non-functional, and sanity testing, also security, smoke, and single-user performance <a href="https://aqua-cloud.io/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=distribution">testing</a>.</p><p>More advanced ones should also have automated, regression, and stress tests.</p><p>This list is missing unit testing. The reason for that is simple: in a healthy situation, it’s the developers’ responsibility to do them before QA gets involved.</p><p>Also, your project would need to use different testing approaches. There are two general kinds: white box tests, where the tester knows the source code, and black box tests, where he doesn’t. Your project will likely need both. There’s also a hybrid approach — grey box testing — outside the minimum scope.</p><p>Automation testing specialists, also known as test automation engineers, are expected to develop, write and maintain automated tests in their respective fields. We’ve gathered the requirements in the picture below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TnKE_V5Hx53KF5LamRRL_Q.png" /></figure><p>Common skills will also be relevant regardless of the QA team structure. To learn what they are, read our <a href="https://aqua-cloud.io/build-qa-team/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=distribution">blog article</a> dedicated to this topic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73ee0531483c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum in Agile testing: what you should know]]></title>
            <link>https://medium.com/@aqua_alm/scrum-in-agile-testing-what-you-should-know-28dc518f44a3?source=rss-49ad0e8bb3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/28dc518f44a3</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[aqua_ALM]]></dc:creator>
            <pubDate>Thu, 27 Oct 2022 00:49:43 GMT</pubDate>
            <atom:updated>2022-10-27T00:49:43.347Z</atom:updated>
            <content:encoded><![CDATA[<p>If you ever were struggling to match the pace and workflows, you probably already know what can help you with that — Scrum. Today we are going to explain how to manage this combination easily. Read on to get practical insights from the world’s leading companies so you can make your software delivery 4 times as fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IsoUIXeXaoS3qnTC" /></figure><h4>Features of Scrum methodology</h4><p><a href="https://aqua-cloud.io/agile-testing-tool/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=scrum-in-agile-testing">Agile Scrum</a> is a software development methodology that combines elements from agile software development and product lifecycle management. Although the name was borrowed from rugby, you shouldn’t take that at face value. While rugby squads organize in three rows that largely do the same thing, every person on the software team usually plays a unique part with varying tasks and responsibilities.</p><p>— Scrum is a process used for teams working on complex products. Teams operate on fixed-length sprints that result in new feature releases. Some go for one-week sprints or even shorter, and some make longer sprints, such as two weeks.</p><p>— Scrum does not mandate how long each sprint should be; it depends on the team and the work happening within that given sprint.</p><p>In contrast, Scrum can adjust in a short period of time. Tasks are added to the backlog, prioritized, and added into the scope of the current sprint. Project Managers usually map out the current sprint and one–two sprints ahead. This means that a non-priority feature request can be implemented in about two months, while something more urgent can be conjured up in a few weeks. When working with agile methodology, most scrum teams observe a balance between the methodology and business needs.</p><p>— Scrum promotes integration between members and reduces errors. All team members share their progress and stay vocal about potential blockers, while the senior staff takes explicit time to help less experienced colleagues.</p><p>— Scrum ceremonies are observed for practical reasons, with specialists collaborating on a project. Daily standups put everyone in the driver’s seat as they share progress and (potential) obstacles. Sprint demos allow everyone — not only engineers — to see progress and work on a visualized goal. Retrospectives are a great asset in improving the workflow.</p><p>Similarly, the team roles are pretty synergetic as well. The product owner is free to turn their vision into user stories. The project manager splits that vision as they turn the user story into tasks. And sometimes, they hire for the role of Scrum master — in agile testing or beyond, their advice keeps everyone to scrum principles.</p><p>To learn <strong>how we use Scrum</strong> in the aqua dev team, feel free to check this <a href="https://aqua-cloud.io/scrum-in-agile-testing/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=scrum-in-agile-testing">article</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28dc518f44a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is your testing strategy good enough?]]></title>
            <link>https://medium.com/@aqua_alm/is-your-testing-strategy-good-enough-273a8195f7b2?source=rss-49ad0e8bb3b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/273a8195f7b2</guid>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[aqua_ALM]]></dc:creator>
            <pubDate>Tue, 25 Oct 2022 13:01:48 GMT</pubDate>
            <atom:updated>2022-10-25T13:01:48.491Z</atom:updated>
            <content:encoded><![CDATA[<p>The<a href="https://aqua-cloud.io/testing-strategy/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=testing-strategy"> testing strategy</a> outlines your company’s approach to quality assurance.</p><p>Any software tester will tell you that there’s no end to testing. But you have to draw the line somewhere. A Software Testing Strategy allows you to do that — outlining your team’s approach to quality assurance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pli6bb-vMPAjRBxjM74mNA.jpeg" /></figure><p>What do you need when creating a testing strategy?</p><ul><li>Objectives — know where you are headed and how this strategy fits in your overall QA approach;</li><li>Planning — understand how much time, money, and other resources you plan to allocate for testing, who will do the work when things need to be done;</li><li>Resourcing plan — have a good idea about what skills your team members have, which technologies and equipment you will use for testing;</li><li>Perception of quality — get on the same page regarding software quality as perceived by developers vs. business stakeholders vs. QAs;</li><li>Test completion criteria — define objectives of each end-to-end test run and scenarios;</li><li>Risk assessment — describe project risks and their impact on testing;</li><li>Test metrics — provide detailed info regarding test coverage metrics in scope;</li><li>Processes — discuss processes behind <a href="https://aqua-cloud.io/it/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=testing-strategy">developing reliable software</a> (what is automated and what isn’t);</li><li>Approach — define the scope of testing various features/components/subsystems, how the product is tested (manual/automated), how bugs are logged, who does what, and so on.</li></ul><p>Here is the <a href="https://aqua-cloud.io/testing-strategy/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=testing-strategy">test strategy</a> sample that is useful to get started with your own strategy:</p><ul><li>Prior to beginning development, meet stakeholders and create a draft of the test strategy;</li><li>Invite them to review and amend the strategy;</li><li>Share the test strategy with the QA team to discuss concerns and potential changes;</li><li>Then adopt the strategy.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWY-gE97bCp7ZxflfXFThQ.png" /></figure><p>See the example of a good test strategy, along with details, below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQXuOI1KrHWV4co3vyQcyA.png" /></figure><p>This list is not exhaustive: it is intended to be a guideline for what a testing strategy should have. Check out our <a href="https://aqua-cloud.io/testing-strategy/?utm_source=medium&amp;utm_medium=article&amp;utm_content=post&amp;utm_campaign=testing-strategy">blog article</a> to find more about testing strategy building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=273a8195f7b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>