<?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 Lauren Mueller on Medium]]></title>
        <description><![CDATA[Stories by Lauren Mueller on Medium]]></description>
        <link>https://medium.com/@laurendmueller?source=rss-479e2bcb8f6c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TLc49mmTafeSvkPXOSr7mQ.jpeg</url>
            <title>Stories by Lauren Mueller on Medium</title>
            <link>https://medium.com/@laurendmueller?source=rss-479e2bcb8f6c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 03:51:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@laurendmueller/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’s Trending: The Cannabis Industry]]></title>
            <link>https://medium.com/@laurendmueller/whats-trending-the-cannabis-industry-4c3368c90cec?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c3368c90cec</guid>
            <category><![CDATA[cannabis]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[influencer-marketing]]></category>
            <category><![CDATA[newsletter]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 16:32:20 GMT</pubDate>
            <atom:updated>2020-09-01T16:32:20.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*k4mf3U6SvewmFxaBE_F_Sg.png" /></figure><p><strong>ThoughtLeaders Weekly Insights</strong></p><p>Welcome to a newsletter dedicated to bringing you the top branded content trends and insights every week!</p><p><strong>What’s Trending: The Cannabis Industry</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/0*6IXjMJFRNU276RS9.png" /></figure><h3>It’s ‘high’ time we treat cannabis like the billion-dollar industry that it has become</h3><p>The growth and impact of the cannabis industry can no longer be ignored as a taboo subject as we move towards conversations of legalization worldwide. That’s why our team at ThoughtLeaders is getting a jumpstart on understanding the challenges the industry faces in the marketing world and emergent trends that will define the future of sponsorships for cannabis brands.</p><p>We’re diving deep into major topics controlling the cannabis influencer space, and you might be surprised to see who is a part of that discussion — hint, your doctor has more in common with the marijuana industry than you previously thought…</p><p>Check out the full report, complete with some pretty graphs, tons of data analysis, and much more!</p><p><a href="https://www.thoughtleaders.io/blog/cannabis-industry-trend-report?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=cannabis_industry_report"><strong>Read</strong></a></p><p>What the industry is talking about:</p><ul><li>Ep. 249 BONUS! A Cannabis Celebration for 4/20 ft. Nidhi Handa of Leune — <a href="http://retrograde.libsyn.com/ep-249-bonus-a-cannabis-celebration-for-420-ft-nidhi-handa-of-leune"><em>That’s So Retrograde</em></a></li><li>103 — The Good, Bad &amp; Ugly of Medical Marijuana and CBD with Dr. Zinia Thomas -<br><a href="http://perryman.libsyn.com/103-the-good-bad-ugly-of-medical-marijuana-and-cbd-with-dr-zinia-thomas">The Low Carb Leader</a></li><li>Puff, don’t pass: The future of weed after coronavirus — <a href="https://mashable.com/article/marijuana-weed-coronavirus-420/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+Mashable+%28Mashable%29">Mashable</a></li></ul><p><strong>Brands that are killing it in the space</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*gmCnqEuhXLgJ3YWk.png" /></figure><p>Thrive Market, a healthy and organic online marketplace, is named in our <strong>Top Brands on YouTube</strong> under the <strong>Health &amp; Fitness</strong> category <br><a href="https://app.thoughtleaders.io/brands/youtube/health-and-fitness/1?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=cannabis_industry_report">See</a> <a href="https://app.thoughtleaders.io/brands/youtube/health-and-fitness/1?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=cannabis_industry_report">Leaderboard</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Z9SdiHY6BVTehT-Y.png" /></figure><p>Care/of, a vitamin supplement subscription box, is named in our <strong>Top Brands in Podcasts </strong>under the <strong>Lifestyle</strong> category <br>See <a href="https://app.thoughtleaders.io/brands/podcast/lifestyle/1?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=cannabis_industry_report">Leaderboard</a></p><p><strong>Listen to our very first episode out now!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SgwBTrydrx6ce46J.png" /></figure><p>Our very own Ariel Burstein, Podcast Host and Account Manager, sat down with David Tintner, CEO and Co-Founder of ThoughtLeaders and former host of The HackingUI podcast.</p><p>They discussed the importance of long-form content and how advertising plays an integral part in helping content creators. David also gave us a glimpse as to what it was like starting a podcast of his own and how he benefits from YouTube and podcast content in his personal life.</p><h4><a href="https://www.youtube.com/channel/UCqrZrbB4r8znMoJp6U289CQ">Watch on YouTube</a> | <a href="https://open.spotify.com/show/4cDkTXwv7CikAxrvmEG6iI">Listen on Spotify</a></h4><p><strong>Our favorite sponsorships</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*sI0uxn5YXGOuhD6B.png" /></figure><p>“My favorite documentaries from Stephen Hawking on time travel…” <em>— CuriosityStream sponsoring on Zach Star YouTube channel</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*DdXh_LMoyL4lvU5N.png" /></figure><p>“Move over, 4/20. 🤭 Turns out, screens are the real culprit behind your red, tired eyes”<em> — Felix Gray sponsoring on The Hustle newsletter</em></p><p><strong>Guess the trend!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1M0SBSO6vTX9eRv5.png" /></figure><p>Can you guess what this trend chart is depicting?</p><p>ThoughtLeaders users can <a href="https://app.thoughtleaders.io/?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=cannabis_industry_report">find the answer here</a>.</p><p>If you’re not a user, what are you waiting for! <br><a href="https://www.thoughtleaders.io/advertiser-demo?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=cannabis_industry_report">Get a Demo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c3368c90cec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ThoughtLeaders Weekly Insights]]></title>
            <link>https://medium.com/@laurendmueller/thoughtleaders-weekly-insights-a65eab99e507?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a65eab99e507</guid>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[influencer-marketing]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[newsletter]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 16:14:15 GMT</pubDate>
            <atom:updated>2020-09-01T16:25:58.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*kJq9nMWLzqeTjbS4qVezHQ.png" /></figure><p>Welcome to a newsletter dedicated to bringing you the top branded content trends and insights every week!</p><p><strong>What’s Trending: Remote Work</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/0*ykAtJm0IriNdcVQG.png" /></figure><h3>If you’re seeing this, you’re probably working from home right now.</h3><p>Take a break from your makeshift office and check out our latest blog post, where we’ve analyzed the #workfromhome trend for brands everywhere. The charts above depict the volume of content mentioning keywords “remote work” and “work from home”.</p><p>The big takeaway? “Brands can really leverage the incredible amount of discussion and activity surrounding #WFH and remote work to deepen brand engagement and optimize their investments.”</p><p>ThoughtLeaders’ proprietary data presents your digital marketing team with an opportunity. If executed correctly, brands can leverage the incredible volume of discussion and activity surrounding #WFH and remote work to deepen brand engagement and optimize their investments. Find out how inside!</p><p><a href="https://www.thoughtleaders.io/blog/the-remote-work-trend-report?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=trend_report"><strong>Read</strong></a></p><p>What the industry is talking about:</p><ul><li>#308a: Everything You Need to Know About Working From Home (But Were Too Afraid To Ask!) with Rachel Hollis — <a href="http://thttps//podcasts.apple.com/us/podcast/308a-everything-you-need-to-know-about-working-from/id594703545?i=1000469784615"><em>Online Marketing Made Easy with Amy Porterfield</em></a></li><li>25 Hilarious Quarantine Memes That Are Getting Us Through This Week — <a href="https://www.jetsetter.com/magazine/quarantine-memes/?source=115964&amp;u=FMUFJAWYKL&amp;nltv=&amp;nl_cs=52007157%3A%3A%3A%3A%3A%3A&amp;mcid=57485">Jetsetter</a></li><li>It’s been emotionally draining: How publishers are adjusting on the fly in a time of uncertainty — <a href="https://digiday.com/media/really-emotionally-draining-publishers-adjusting-fly-time-uncertainty/"><em>Digiday</em></a></li></ul><p><strong>Brands that are killing it</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*vLkgZy7jvLjtxZSA.png" /></figure><p><a href="https://www.thoughtleaders.io/blog/6-wellness-apps-that-use-podcast-sponsorships?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=trend_report">6 Wellness apps</a> that use Podcast sponsorships to fuel their growth</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-p9c1rjSEMEV8Cbb.png" /></figure><p><a href="https://www.thoughtleaders.io/blog/5-cosmetic-brands-that-successfully-capitalized-on-beauty-trends-on-youtube?utm_source=newsletter&amp;utm_medium=email&amp;utm_campaign=trend_report">5 Cosmetic brands that successfully capitalized on beauty trends on YouTube</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*MIHjNM238xvell3I.png" /></figure><p><a href="https://www.thoughtleaders.io/blog/6-innovative-brands-redefining-the-fitness-world?utm_source=newsletter&amp;utm_medium=email&amp;utm_campaign=trend_report">6 Innovative brands redefining the fitness world</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*AzUalnSxet9swUcE.png" /></figure><p><a href="https://www.thoughtleaders.io/blog/5-health-brands-using-sponsorships-to-reach-new-customers?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=trend_report">5 Health brands</a> using sponsorships to reach new customers</p><p><strong>Our favorite sponsorships</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*4SH7vP5UxVRr6Ssv.png" /></figure><p>Machine learning online boot camp offering 1:1 mentorship over online conferencing <em>— Springboard sponsoring on Python Programmer YouTube channel</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*4v8VdRlVKjL63qkx.png" /></figure><p>“The sudden shift to remote work is throwing a wrench in some companies’ gears”<em> — Conga sponsoring on The Hustle newsletter</em></p><p>Originally published by Lauren Mueller, Account Manager @ <a href="https://www.thoughtleaders.io/?utm_source=newsletter&amp;utm_medium=medium&amp;utm_campaign=trend_report">ThoughtLeaders</a> on April 16, 2020</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a65eab99e507" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Test Design: The Foundation for Effective Test Automation | TestCraft]]></title>
            <link>https://medium.com/@laurendmueller/test-design-the-foundation-for-effective-test-automation-testcraft-fedf73c08f38?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fedf73c08f38</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Thu, 18 Jul 2019 11:13:20 GMT</pubDate>
            <atom:updated>2019-07-25T13:03:59.556Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OicKbd6GnubPPECZ.jpg" /></figure><p><em>This is the first post in an upcoming series about how to best design and structure your test scenarios with TestCraft. This post gives a general overview of best practices for test design.</em></p><p>Anyone looking to go into test automation has at some point asked themselves the following question: Is coding experience required to succeed in the field? This question has <a href="https://ministryoftesting.com/dojo/lessons/software-testing-shouldn-t-require-expert-coding-skills">sparked a lot of controversy</a> in recent years, with people passionately defending either side of the argument.</p><p>Let us be clear: testers can use code for a variety of purposes related to testing. For example, knowing how to read code as a tester can be very helpful if you’re looking to <a href="https://www.testcraft.io/participating-code-reviews-tester-webinar-recap/">get more involved in code reviews</a>. There are many instances when knowing how to read (or even write) code at a basic level can help you develop a more well-rounded understanding of test automation. Yet, we believe that there are other skills that are important, even critical for your test automation efforts to really thrive.</p><h3>The Importance of Designing Tests Effectively</h3><p>We at TestCraft believe that a major key to effective test automation is in the test design. Designing your tests properly will not only best prepare you for finding vulnerabilities in your software but also setting yourself up for scale. No matter which tool you use for your automation needs, good test design will ultimately be what impacts how your tests perform in the future.</p><p>With that in mind, here are some of our best practices to consider when it comes to designing tests effectively:</p><h3>Test Design Rule #1 — Keep Your Tests Short and Simple</h3><p>When thinking of how to design your tests, make sure that they abide by the <a href="https://en.wikipedia.org/wiki/KISS_principle">KISS principle</a>: Keep It Simple, Stupid. Keeping your tests short throughout your test automation efforts will ultimately serve you well, whether you’re just starting out with more basic tests or moving into more complex scenarios. This will not only make your testing easier, but it can also help your testing <a href="https://www.testcraft.io/connecting-manual-testers-devops-webinar/">integrate more into your company’s DevOps lifecycle</a> in the future.</p><p>No matter what you’re testing, we recommend keeping your automated tests between 5–15 steps so that they’re simple and easy to understand. Each component within these tests should also clearly explain its function. This is especially important when multiple teams see and provide feedback on these tests. As a benchmark, share your test with someone from another team who is less familiar with your test. If that person can understand what your test is trying to accomplish and the steps it is taking to get there, you can rest assured that your test components are clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z062tlqePprT04lMQM6wVQ.png" /></figure><h3>Test Design Rule #2 — Build Your Tests From Reusable Components</h3><p>One great way to keep your tests simple is by reusing the same components when building them. There’s no need to recreate the wheel every single time you want to design a new test scenario. Once you have built those first few, simpler tests, you should use those components for future scenarios.</p><p>Consider this example: you design a test that checks your login process. In all other test scenarios that require someone to log in to their account, such as an account creation test, modify account test or even very complex scenarios, you can then reuse this login test as a step within all these test options.</p><p>Reusing components is beneficial for multiple reasons. First, it ensures that your tests go through the same elements when testing different functions. This mimics the end user more closely by broadening the different ways that someone can interact with your application. Second, it helps a lot with test maintenance. <a href="https://www.testcraft.io/product/">Within TestCraft specifically</a>, if you create a test element multiple times that test the same function, the platform will merge the two elements automatically. In addition, changes that you make to one element will apply automatically to other tests that use it. This can help reduce your overall maintenance time tremendously.</p><h3>Test Design Rule #3 — Every Test Should Be Independent</h3><p>Another important point to consider when designing tests is that they <a href="https://dzone.com/articles/writing-good-tests">should be independent of other tests</a> that you have in your environment. Tests can then be executed in isolation, without relying on external factors. Keeping your tests independent also prevents unnecessary test breakage. If feature B changes in an application under test, there should be no need to update the tests for feature A to ensure that it continues to run.</p><p>Even when you’re reusing components, tests should still be independent. The key is to make sure that the test goes through the entirety of the process that you’re analyzing. As an example, if you’re looking to test a scenario where an end user modifies his or her account, that test should include the login and account creation scenarios described above as test steps. Since modifying an account would first require creating an account, account creation would need to be part of your test.</p><p>To ensure that all of your tests are independent, check that your test includes these three components: <strong>navigation</strong>, <strong>operations</strong>, and <strong>validations</strong>. Each test should navigate to the necessary part of your application, do some sort of action after it goes there, and then validate that the task was either completed or get results for why it wasn’t. Keeping these three components in mind will make your tests more durable in the long run.</p><h3>Test Design Rule #4 — All Tests Should Have a Purpose</h3><p>Another important best practice to keep in mind is that each test that you design should always have a clear purpose. While this may seem obvious, the purpose of the test can often get lost either over time or when multiple testers or teams are involved in building the test. Defining a purpose at the start of the design process and identifying that as a clear goal throughout the design will make sure that your <a href="https://www.testcraft.io/test-automation-aging-continuous-testing/">tests continue to stay relevant</a> and helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c3ygXfoesq91pvifPCMaqA.jpeg" /></figure><p>To prevent your test from getting off-track, it’s a good idea to create the test as if you won’t be the person testing the application next time. This mindset will put you in the shoes of a future team member, or even you in a few months’ time, who doesn’t know or remember the context of the test inside and out. This will prompt you to make the purpose of the test clear and solidify its place in the rest of your environment.</p><h3>Test Design Rule #5 — Don’t Forget the End User</h3><p>Last but not least, the end user should always come first when designing tests. Especially as a business tester, you know your application inside and out. You understand the different ways your customers or prospects interact with your application, along with their requirements and pain points. Designing your tests with your customer in mind will ultimately lead you in the right direction when doing effective test automation.</p><p><a href="https://checkpointech.com/think-like-an-end-user/">Keeping your end users in mind</a> will also help when mitigating risk. When designing your tests, focus on different ways a user can break it. Some ways that end users can break tests might be obvious, while others could be due to technical things that end users will never see but can cause problems. Knowing these ahead of time will make sure that you’re both choosing the right tests to design and designing them smartly.</p><h3>Good Test Design Leads to Better Test Automation</h3><p>In this article, we delved into some important best practices for designing tests. When it comes to what testers need in order to excel in test automation, smart and intuitive test design is absolutely essential. By implementing these test design skills, you will be setting your test automation up for success.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/test-design-foundation-effective-test-automation/"><em>https://www.testcraft.io</em></a><em> on July 18, 2019 by Danielle Felder.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fedf73c08f38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 QA Blogs You Need To Follow (If You Aren’t Already) | TestCraft]]></title>
            <link>https://medium.com/@laurendmueller/7-qa-blogs-you-need-to-follow-if-you-arent-already-testcraft-1d6570a895ea?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d6570a895ea</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[blog]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Wed, 15 May 2019 11:49:19 GMT</pubDate>
            <atom:updated>2019-07-25T12:39:32.762Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*odah3hdVuBnWjMhG.jpg" /></figure><p>There is always more to learn when it comes to QA and software testing. From staying on top of the latest trends to honing your skills, QA blogs can provide great advice and insights.</p><p>While there are many great resources out there, it can feel overwhelming to know which thought leaders to trust when navigating the world of testing experts. To help you out, here are the top seven blogs that we think you should keep on your radar.</p><h3>Joe Colantonio</h3><p>A big believer in a full-stack approach to automation, <a href="https://www.joecolantonio.com/">Joe Colantonio’s blog</a> delves into the different ways test automation can impact your QA team. He covers a wide range of topics, from DevOps to the way you set up and provision your environment. Through his writing, he focuses on how to incorporate automation into all areas of the software development lifecycle. In his podcast, TestTalks, you can also find his interviews with some of the biggest leaders in the testing industry. If you’re looking to invest in automation testing and performance testing tools, he writes product reviews on his blog as well.</p><h3>Angie Jones</h3><p><a href="https://angiejones.tech/">Angie Jones’ blog</a> is a must-read for anyone who is looking to incorporate test automation into their software testing strategy. She writes about everything from industry trends in test automation and building a top-notch QA team. She also focuses on best practices and techniques, like how to build an automation framework that is agile-friendly. For those of you who are more hands-on, you can find her free test automation courses on the blog as well.</p><h3>Eran Kinsbruner</h3><p>If you like continuous testing, <a href="https://continuoustesting.blog/">Eran Kinsbruner’s blog</a> is a must-follow. He writes about everything related to this topic, with a focus on web and mobile applications. An industry veteran, his blog is also a great resource for dealing with each step of the application development cycle.</p><p>He’s a frequent speaker at global QA and testing conferences and guest writes for many different publications. Make sure to keep an eye out for his articles on the <a href="https://www.testcraft.io/blog/">TestCraft blog</a> as well!</p><h3>Chris Kenst</h3><p>If you’re looking QA blogs that offer a consistently updated list of software testing conferences and workshops, <a href="https://www.kenst.com/">Chris Kenst’s blog</a> is the place to look. An automation engineer for BloomNation, Kenst also writes about all things software development and testing. He’s passionate about teams achieving fast, “shippable quality” for their companies and offers many practical examples for doing just that.</p><p>Be sure to keep an eye out for his speaking engagements as well, including his <a href="https://www.testcraft.io/webinar-participating-code-reviews/">upcoming webinar</a> (with TestCraft). If you’re looking to learn how to conduct code reviews as a tester, this is the webinar for you.</p><h3>The Friendly Tester</h3><p><a href="https://thefriendlytester.co.uk/">Richard Bradshaw’s blog, The Friendly Tester</a>, discusses everything from automation testing to his own growth as a software tester. As the CEO (also known as “FriendlyBoss”) of <a href="https://www.ministryoftesting.com/">Ministry of Testing</a>, Bradshaw also offers unique insights into the software testing community at large. His mixture of testing tips and personal musings make this a great QA blog to follow. Make sure to also check out his “Whiteboard Testing” YouTube channel, which has videos on different software testing best practices.</p><h3>Evil Tester</h3><p>Contrary to what you might think, Alan Richardson did not name <a href="https://www.eviltester.com/">his blog “Evil Tester”</a> in response to the “Friendly Tester” blog mentioned above. Rather, he sees “evil testing” as a fundamental attitude shift where testers actually take responsibility for how they test. Instead of acting passively, Richardson believes that testers should own their processes and ways of thinking when doing software testing.</p><p>Unlike other QA blogs, Richardson focuses on this change in attitude, combined with skills overviews and other tips to approach testing in a more pragmatic way. This is the blog for you if you’re looking for professional advice coupled with some life lessons.</p><h3>Satisfice</h3><p>James Bach’s blog for his consulting business, <a href="https://www.satisfice.com/blog">Satisfice</a>, focuses on different applications of his Rapid Software Testing methodology using the Context-Driven School (CDS) of software testing thought. Rather than focus purely on the rote formalization of technical work, this approach prioritizes skills and problem-solving. Coming from a programming background, Bach’s blog offers a unique outlook that appeals to both testing professionals and engineers.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/qa-blogs-you-need-to-follow/"><em>https://www.testcraft.io</em></a><em> on May 15, 2019 by Danielle Felder.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d6570a895ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Testing Leaders, 2019 Is Your Year for Transformation]]></title>
            <link>https://medium.com/testcraft/software-testing-leaders-2019-is-your-year-for-transformation-557662afe6a5?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/557662afe6a5</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 15:18:08 GMT</pubDate>
            <atom:updated>2019-02-20T09:00:36.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*08H8RRN5gSvIMWNjUndIQw.png" /></figure><p>When you ask high-level managers, CIOs, VP R&amp;Ds, and others what their greatest goals and objectives are, they will all state that maturing their DevOps processes, <strong>releasing software and innovation fast and with confidence</strong> is among their top of mind. Here, I am not specifically referring to unit testing that would typically be owned by developers, but mostly on the rest of testing that includes functional UI testing, regression tests, and more.</p><p>When you double down on the above goals and ask, “<strong>what is blocking you from succeeding</strong>”? — the main answer is that the pace of development and innovation isn’t in line with the organization team to test and validate the changes. Adapting seamlessly and in an automated fashion to software changes is a great challenge.</p><p>As stated in recent on an ITPROPortal <a href="https://www.itproportal.com/features/cios-share-why-software-testing-matters/">article</a>, “<strong><em>DevOps enables innovation, however, testing can hold it back</em></strong>”.</p><h4>Why is Software Testing so Hard?</h4><p>To break down the main points for why software testing in the era of digitalization and DevOps is so difficult, we will investigate the following reasons:</p><ul><li>Business testers, Manual testers skillset</li><li>Unstable test automation for mobile and desktop web apps</li><li>Lab-related issues around scaling of resources to reduce test execution time</li><li>Time to analyze results and fast feedback from testing back to development</li><li>Flaky tests noise</li></ul><p>When testing is the weak chain in the software delivery pipeline, there is a clear call to action with logical responsibilities to fix that problem.</p><h4>The Opportunity for Test Management to Lead Change</h4><p>To solve the biggest pain in DevOps, test managers and directors of QA ought to step up and influence. From a skillset perspective, the test management persona is very well positioned to drive change, since she from the entire organization understands the root causes of the difficulty behind testing. These managers used to be in the tester’s position a few years ago themselves.</p><p><strong>Management needs to address the 4 main pillars:</strong></p><ol><li>Test Authoring Simplification</li><li>Test Automation Coverage</li><li>Test Execution Velocity</li><li>Better Test Reporting and Fast Feedback</li></ol><h4>Test Authoring Simplification</h4><p>In this bucket, the main problems testing leaders or managers are facing today are among the skill set their testers to have. Such skills often block them from automating as much as they would like to. To improve this situation, test managers can do the following:</p><ul><li><a href="https://www.testcraft.io/community/">Provide very focused and professional test automation mentoring with training, books, conferences, and more</a>. TestCraft has set up a community just for that, <a href="https://www.testcraft.io/machine-learning-meetup-lp/">here</a>.</li><li>Managers should hire great employees, and should leverage their skills, guide them, and match the market products to employee skills.</li><li>Offer these testers alternative tools to ease the test authoring process (codeless, record &amp; replay, BDD backed by blackbelt test architects or developers etc.)</li><li>Continuously measure, proof and enhance the skills of the testers, so they excel over time.</li><li>Embed them as soon as possible in the continuous delivery pipeline activities, allow them to contribute to the continuous integration testing, and more.</li></ul><p>Because of the above, testing leaders will be able to build trust in the test that is produced regardless of their nature, the tool that was used to develop them, and the employees varying skills.</p><h4>Test Automation Coverage</h4><p>The digital landscape today is more complex than ever before. That’s why automating all possible use cases and test flows is hard, sometimes not even reasonable from time and ROI perspective. With that in mind, it is imperative to note that <a href="http://www.testcraft.io/">robustness of tests</a> takes priority on quantity. Stabilize, build trust in the tests and scale up. This will get the best results from velocity and overall quality perspective.</p><p>To address such pain test managers can lead through change by the following possibilities:</p><ul><li>Build or leverage quality dashboard that shows exactly where are the missing test automation code, and bring these cases to the table to raise their priority</li><li>Perform ongoing test suite reviews to understand if the test coverage is really reflecting the latest product features and scope, then, adjust the test development plans accordingly.</li><li>Leverage easy test authoring tools that can pick missing test automation flows that are either performed manually today or are constantly flaky and failing to cause false negatives.</li><li>Better plan the future software iteration in sync with product management, development leaders so it leaves room to close test automation coverage gaps.</li></ul><h4>Test Execution Velocity</h4><p>To speed up release cycles and remove the testing bottleneck, teams must test faster. Testing faster is controlled by the level of lab and cloud commuting they have at their disposal. Automating the entire process including infrastructure set up as it shouldn’t be set up per execution. Velocity means on top of the testing at scale, and the test results analysis (that also separately serves 2 goals — debugging and decision making, as well as velocity).</p><p>Executing hundreds of test flows in a very short amount of time while the test engineers need to setup multiple smartphones, tablets, desktop VMs with endless permutations running against 2–3 test environments (QA, staging, production) can be a huge time suck and a pain if there isn’t an efficient lab in place. Here, test managers can embed a <a href="http://www.perfecto.io/">centralized lab in the cloud</a> backed by strong enterprise cloud providers that can enable running endless tests on unlimited desktop and mobile platforms with confidence. Such labs have SLA, they are always on and always available, secure and up to date with all the recent market platform releases.</p><h4>Better Test Reporting and Fast Feedback</h4><p>Last, but not least, test managers today are challenged with a constantly increasing pile of test data. Such an amount of data is impossible to analyze, realize, and act upon in a timely manner. Such thing results in a decreasing level of value coming from the test artifacts. Test managers should introduce <a href="https://www.perfecto.io/platform/test-automation-reporting-analytics-digitalzoom/">smarter test reporting</a> and analysis, backed by machine learning to help drive fast feedback, reduce noise, and better serve the entire DevOps pipeline.</p><h4>Bottom Line</h4><p>In 2019, testing leaders and QA managers are best positioned to unblock the entire DevOps pipeline blockage. To do so, they should put the above objectives as keys for success. Each bucket in the above can be improved significantly through initial baby steps. Once these steps are proven to help, they can be much heavily enhanced to solve the bigger picture.</p><p>Software testing leaders, this is your time to shine!</p><figure><a href="https://www.testcraft.io/machine-learning-meetup-lp/"><img alt="" src="https://cdn-images-1.medium.com/max/800/0*2AlM6nplPIJoXsFD.png" /></a></figure><p><em>Originally published at </em><a href="https://www.testcraft.io/software-testing-leaders-2019/"><em>www.testcraft.io</em></a><em> on January 14, 2019, Eran Kinsbrunner.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=557662afe6a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/software-testing-leaders-2019-is-your-year-for-transformation-557662afe6a5">Software Testing Leaders, 2019 Is Your Year for Transformation</a> was originally published in <a href="https://medium.com/testcraft">TestCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing in Production: It’s Time]]></title>
            <link>https://medium.com/testcraft/testing-in-production-its-time-66f1c96dad36?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/66f1c96dad36</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Thu, 03 Jan 2019 10:26:55 GMT</pubDate>
            <atom:updated>2019-02-20T09:25:00.167Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tpqLpyL1ZwYofnb3E9aOTg.png" /></figure><p>In the world of deployment to the cloud, distributed applications and microservices, agile and DevOps methodologies, there is no longer a life cycle phase devoted to traditional functional testing. Much of the testing becomes automated, from unit tests to smoke tests to system tests, but we have less and less functional and exploratory testing, and no phase of the lifecycle devoted strictly to testing.</p><p>Moving fast is a mantra in modern software methodologies; we deploy without full hands-on testing but have the ability to rapidly revert to an earlier “good” version. In the process, we are leaving some aspects of the quality behind.</p><p>When that application is in production, we have to know when it is in trouble, and just what that trouble is, to understand the nature of the problem and have some data for diagnosis and repair. Even today, many cloud teams simply check whether or not their application is still operating using a continuous “ping” command, without information on performance or the availability of specific operations. In fact, all a ping tells IT and the application team is whether or not the server/instance is still running, not how healthy it is.</p><h4>Ways to Test in Production</h4><p>Teams need more information than that if their goal is to have a high-quality application. A collection of techniques known collectively as application <a href="https://www.testcraft.io/monitoring/">monitoring</a> is the way to do so. Application monitoring encompasses a wide range of testing and data collection activities. Synthetic testing lets teams record and execute tests representing how users might use the application. These tests can run at different times of day, and typically from different locations around the world.</p><p>Monitoring in production also incorporates real user monitoring or RUM. RUM is just what the term implies — in real time, it looks at user requests coming in, and what is returned in response. When you profile across a large sample of users, you get a good picture of how actual users perceive and how they use your application.</p><p>Last, monitoring can include tracing individual transactions through the different components and tiers of the application. By tracing a transaction, you can look at code pathways and see what code is being exercised during a user session. This is useful in finding defects and slow code, as well as understanding what features are more commonly used.</p><p>While major cloud providers such as, Amazon with CloudWatch and Google with Stackdriver, have their own tools that perform at least some application monitoring functions, independent software companies such as AppDynamics, New Relic, Dynatrace, and some <a href="http://www.testcraft.io/">TestCraft</a> integrations provide more complete monitoring solutions.</p><h4>Production Monitoring is Testing</h4><p>Why is this a function of the software tester? It’s not only something a tester should be doing, but it also will be one of the two or three things that will make up almost every testing job in the future. Unless we want the professional practice of testing to gradually fade away, it must adapt to new ways of building applications and managing the application lifecycle.</p><p>Think of production monitoring as shifting testing to the right. We talk a lot about shifting left, where more testing occurs earlier in the development process. That’s fine and important, but testing is almost always incomplete when an application is deployed in a DevOps or agile team because new features are rushed to the production build. How do we make up the testing, especially if we are deploying regularly or even continuously?</p><p>Simply, we do so when the application is in production. We find ways to look for defects and poor performance after the application is serving real users. Using application monitoring techniques, testers can use real data to find and diagnose application errors quickly, and with information that is derived from the actual production environment.</p><h4>Testing in Production as the future</h4><p>The idea of testing continuing into production bothers many testers because testing has traditionally verified the quality of the application prior to release to production. However, thanks to agile and DevOps, testing is changing radically, and testers have to look at the best way to change. Engaging the application at all times during development and deployment is the most promising way of doing that.</p><p>Testing in production is in the future of testing. Testers will continue to do traditional test activities, especially exploratory testing. Automation has proven itself valuable in functional testing, by enabling testers to spend less time on rote manual testing. And AI will provide yet-undefined benefits across the testing process.</p><h4><em>Originally published at </em><a href="https://www.testcraft.io/testing-production/"><em>www.testcraft.io</em></a><em> on January 3, 2019, by Peter Varhol.</em></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66f1c96dad36" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/testing-in-production-its-time-66f1c96dad36">Testing in Production: It’s Time</a> was originally published in <a href="https://medium.com/testcraft">TestCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2018 Software Testing Year In Review]]></title>
            <link>https://medium.datadriveninvestor.com/the-2018-software-testing-year-in-review-200b2fe99d6b?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/200b2fe99d6b</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[2018]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Wed, 19 Dec 2018 08:56:24 GMT</pubDate>
            <atom:updated>2019-01-17T16:21:14.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="http://www.track.datadriveninvestor.com/1B9E"><img alt="" src="https://cdn-images-1.medium.com/max/700/0*D_NWVs76Snis1sHe" /></a></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77pdW92VSG1g6THdHV7iaA.png" /></figure><h4>The 2018 Year In Review — In the Software Testing Industry</h4><p>There you have it, another year has gone by. It’s time to look back and discover what we accomplished. We, the software testing industry, had a prosperous year full of new and reinforced trends, successful acquisitions, and a great deal of funding. See this year’s funding and acquisitions below in our infographic, made specifically for you.</p><p>The 2018 testing arena garnered up more than $300M worth of funding. The timeline, below, indicates this year’s announced investments and acquisitions. All information given are the disclosed amounts and news.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*NvVUaB88SGbYtZTTdoINEg.png" /></figure><h4>2018 Software Testing Trends</h4><p>The biggest change in our industry is the implementation of AI and ML-based technology, this followed by a normalization of test automation. Let’s look back on those trends that took 2018 by storm.</p><h4>Machine learning and artificial intelligence in testing</h4><p>AI and ML are terms heard almost every day in any industry. Whether it is in healthcare, retail, transportation or testing, AI is either feared or adored. This phenomenon is clearly helping industries of all walks of life. Although when it comes to the software testing field, there is still some hesitation and concern. Testing isn’t as straightforward as it once was because of the Agile pace the industry brought on in the past couple of years. The abundance of data to handle has multiplied and the time to release has shortened. Their lies a whole new approach, one allowing the modern tester to handle a continuous workload powered by ml-based tools.</p><p>Artificial intelligence and machine learning are slowly but surely becoming crucial segments in QA and in the software testing world as a whole. Machine learning brings more accurate results to the tester and divides time spent on creating and managing test cases in half. For example, <a href="https://www.testcraft.io/machine-learning-used-test-automation/">TestCraft’s ML-based algorithm</a> is able to automatically overcome changes in the app and keep tests from failing. This allows our platform to overcome 97.4% of the changes in the app (changes that were not caused by a change in the app logic or process). Now testers are following suit on this trend and are opening their eyes to ML-based software.</p><h4>Test automation as the standard</h4><p>In recent years we’ve all heard that test automation is vital to continuous integration. Although test automation has always been part of the conversation it was never truly accepted by all, similar to ML/AI-based tools now, until now. 2018 was the year test automation became the new norm. According to <a href="https://www.gartner.com/doc/reprints?id=1-5V82COP&amp;ct=181128&amp;st=sb?mkt_tok=eyJpIjoiTnpCbU9EWmxORGxqTURCaiIsInQiOiJ5TW4zdUQ2VTlVbkZIXC9qS2J2eUxcL3RcL0pcL1RQKzJPK1hpV0w5b1RrdUtVVVR2S01cLytFRnZnems5alNocllcL3dmUUZkdUJnRUZwa1BaNHhUVkxYVEU0VUlYa1RXUitpejZ5OWpmVnhBeGdxbmMyVmZqRDNkVjlzUUh3Sk9NbkZVUSJ9">Gartner’s Magic Quadrant for Software Test Automation</a> report, “In 2017, 57% of respondents named Hewlett Packard Enterprise (HPE) when asked “What other vendors were considered?,” followed by Selenium. In 2018, Selenium came out on top with 43% — with the next four vendors coming in between 18% and 24%.” This show more organizations are leaning toward Selenium, test automation, as the most viable solution for their testing teams.</p><p>The demand for <a href="https://www.testcraft.io/">test automation</a> is exponentially growing because of the time-to-market factor. Artificial intelligence and machine learning are gaining traction for the same reason test automation is the new common practice. Gartner says, “during the next three years, (they) expect that AI, ML, predictive analytics and RPA will play an increasing role in software testing and automation”, and we couldn’t agree more!</p><p>Let us know if you have other mentionable trends on any of our social media sites.</p><p>Happy holidays and have a great new year!</p><p>Here are the sources we used to find the data and investments of the testing world:<a href="https://www.gartner.com/doc/reprints?id=1-5V82COP&amp;ct=181128&amp;st=sb?mkt_tok=eyJpIjoiTnpCbU9EWmxORGxqTURCaiIsInQiOiJ5TW4zdUQ2VTlVbkZIXC9qS2J2eUxcL3RcL0pcL1RQKzJPK1hpV0w5b1RrdUtVVVR2S01cLytFRnZnems5alNocllcL3dmUUZkdUJnRUZwa1BaNHhUVkxYVEU0VUlYa1RXUitpejZ5OWpmVnhBeGdxbmMyVmZqRDNkVjlzUUh3Sk9NbkZVUSJ9"> Gartner Magic Quadrant for Software Test Automation</a>, <a href="https://en.globes.co.il/en/article-application-visual-management-co-applitools-raises-31m-1001232260">Globes</a>, and <a href="https://www.crunchbase.com/">Crunchbase</a>.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/2018-software-testing-year-review/"><em>www.testcraft.io</em></a><em> on December 19, 2018, by Lauren Mueller.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb2a0d6%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb2a0d6%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/0707f5c806284d01a4a13c7b13a91ce3/href">https://medium.com/media/0707f5c806284d01a4a13c7b13a91ce3/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=200b2fe99d6b" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/the-2018-software-testing-year-in-review-200b2fe99d6b">The 2018 Software Testing Year In Review</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Key DevOps and Software Testing Predictions for 2019]]></title>
            <link>https://medium.com/testcraft/5-key-devops-and-software-testing-predictions-for-2019-5ab129c05fdd?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ab129c05fdd</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[2019]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Tue, 18 Dec 2018 12:19:44 GMT</pubDate>
            <atom:updated>2019-01-17T09:32:27.966Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjFgN3OccMsZGs9l7UNwKw.png" /></figure><p>2018 was an exciting year from an innovation perspective, from a DevOps maturing standpoint, and from the planting of roots around <a href="https://www.testcraft.io/machine-learning-used-test-automation/">AI and ML</a> in various use cases in the DevOps landscape.</p><p>With that in place, organizations are still struggling to increase the degree of their digital test automation for both desktop web apps, responsive and progressive, as well as mobile native apps. The maturity of agile and DevOps processes together with stable continuous testing are among the key challenges’ teams are facing.</p><p>In 2019, there will be few significant advancements in the software industry that will enhance the overall maturity in DevOps and <a href="http://perfecto.io/">Continuous Testing</a>.</p><ul><li>The role of the DevOps tester</li><li>DevOps adoption will see (even) more growth</li><li>ML and AI will permeate into both dev and test tasks</li><li>Digital transformation and UX will grow with AR/VR/5G and IoT technologies</li><li>Focus on non-functional testing activities within the DevOps Pipeline</li></ul><h4>The role of the DevOps tester will continue to grow</h4><p>Currently, the industry is divided into 3 types of personas that are involved in the testing processes. The <strong>software developer</strong> who focuses on unit testing and build acceptance testing, the <strong>test automation engineer</strong> who is focused on test coding of functional and non-functional test development, and lastly, the <strong>business tester</strong>, who is focused on the user stories from a manual standpoint. In 2019, the main impact will be on the software developers and the business testers. These personas will aim to enhance their overall test productivity by shrinking to the minimum possible time it takes to author and execute their tests. To accomplish that, these teams will embrace smart testing tools that are powered by machine-learning and artificial intelligence capabilities. Among the features these personas will benefit from will be codeless test authoring, smart test data analysis, self-healing of test code while the app is dynamically changing, and more.</p><p>To succeed in the above, these individuals need to explore the existing tools and try to match their capabilities with the most urgent and tedious tasks that are on their tables. Starting small and growing the adoption of these tools will be a key to success. From recent <a href="http://blog.qatestlab.com/2018/11/06/testing-trends-2019/">research</a> among many others, it seems like DevOps teams are already focusing on the above objective (see following image), so 2019 will be a great year to validate whether this will be the groundbreaking trend of the year in DevOps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SB-oxhJcgDtK_1rnZG0JAg.png" /></figure><p><em>Fig 1: Use of Bots Interest as Part of Test Activities (Source: </em><a href="http://blog.qatestlab.com/2018/11/06/testing-trends-2019/"><em>QATestlab</em></a><em>)</em></p><h4>DevOps adoption will see (even) more growth</h4><p>DevOps is here for a while and is the focus of most software engineering management across industry verticals. In 2019, to drive more agility, and expedite delivery of value to customers, DevOps teams will embrace various tools and technologies that will boost their productivity even further. Among the changes we will see are:</p><ol><li>Higher focus and investment in the <strong>automation</strong> of the entire DevOps pipeline activities from coding through production.</li><li>More cloud and SaaS-based services that include lab environments, service virtualization, big-data management, and more.</li><li>Maximizing software architecture around <strong>micro-services development.</strong></li><li><strong>Business analytics</strong> visibility at any stage of the software development lifecycle to ensure business-focused feature delivery.</li><li><strong>ML and AI </strong>solutions in various use cases will help deliver and measure software quality</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*w25E5na808CT5yNBBZdoLQ.png" /></figure><h4>ML and AI will permeate into both dev and test tasks</h4><p>As mentioned above, and as a key supporter of the entire DevOps pipeline tasks, ML and AI tools will come to the rescue among various use cases that the above-mentioned 3 personas require.</p><ol><li>Reliable and stable test automation authoring to facilitate trust between dev and testers. Tools that enable <strong>codeless testing</strong> with self-healing object management will see higher adoption within DevOps teams.</li><li><strong>Optimization</strong> of <strong>test</strong> <strong>suites</strong> across the entire DevOps pipeline through identification of flaky, redundant, and duplicate cases.</li><li><strong>Slicing and dicing test data</strong> to help decision-makers validate their software quality on-demand. Understand functional areas quality fast, identify RCAs (root cause analysis) of defects fast, present quality dashboards including visibility into the CI (continuous integration), logs visibility and analytics, traceability between tests and requirements, and more.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*1vX4Qf95fesN93HGVoq6hw.png" /></figure><h4>Digital transformation and UX will grow with AR/VR/5G and IoT technologies</h4><p>Continuous testing in the digital era has never been more complicated, and 2019 will take this a step further as we start learning more about advanced AR/VR capabilities in the mobile and web landscape, and the rollout of 5G networks that will aim to boost end-user experiences.</p><p>Technology gaps between mobile and web will shrink even more with the rise of <a href="http://www.onlinetestconf.com/sessions/eran-kinsbruner-tips-and-tricks-to-approach-reactiveprogressive-app-testing-projects/">progressive web apps</a> (PWAs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*cGn5enxQObVlGSjaAFerLg.png" /></figure><p>To keep pace with the innovations, DevOps teams will need to re-think schedule, existing software delivery processes, and existing architecture and find ways to accommodate these changes within the already tight delivery schedules they face today. Automation here will be the key, and enabling it through the right tools, test environments, labs, and others will serve as a key to success.</p><h4>Focus on non-functional testing activities within the DevOps pipeline</h4><p>While teams struggle to automate their DevOps pipeline and include as many tests as possible from the unit, acceptance, and functional testing, in 2019, the expectations will grow as more compliance with non-functional standards like accessibility and security become mandatory.</p><p>The above-mentioned new technologies do not come free, and to support the new 5G network, AI/ML, AR and VR, IOT and others, teams will need to spend more time on developing test cases to cover the innovative features. By end of 2019, all websites need to comply with the strict accessibility requirements and to make this less painful and impactful on the overall pipeline, these tests will need to be automated as much as possible. Security and cyber attacks are always in the news, but the risks are only going up as the digitalization matures, hence, teams will invest more time and resources into baking security testing, code scanning etc. during 2019. Overall reliability, UX, and performance testing of apps will also become an integral part of the DevOps pipeline and part of the CI testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*KgfZabZfrP1Q2-JkQg95LQ.png" /></figure><h4>Bottom Line</h4><p>As we wrap 2018, it is obvious that the future of DevOps and continuous testing holds both exciting innovations and challenges. Being able as a team to enter 2019 as prepared as possible for both, will help drive faster value to customers, with greater quality and greater productivity.</p><p>Happy New Year!</p><p><em>Originally published at </em><a href="https://www.testcraft.io/5-devops-software-testing-predictions-2019/"><em>www.testcraft.io</em></a><em> on December 18, 2018, by </em>Eran Kinsbruner<em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ab129c05fdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/5-key-devops-and-software-testing-predictions-for-2019-5ab129c05fdd">5 Key DevOps and Software Testing Predictions for 2019</a> was originally published in <a href="https://medium.com/testcraft">TestCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ML & How Manual Testers Should Adapt to the DevOps Era]]></title>
            <link>https://medium.com/testcraft/ml-how-manual-testers-should-adapt-to-the-devops-era-b27f5015eeae?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b27f5015eeae</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 14:41:24 GMT</pubDate>
            <atom:updated>2018-10-22T14:18:02.736Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Manual Testers Should Adapt to the DevOps Era</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAzUue8xTMPBZx9ZKW9HBg.png" /></figure><p><em>The industry is shifting towards a more automated software development and testing processes. This trend, however, threatens to eliminate the need for testers whose main job is to manually execute large amounts of tests. Although testers have important contributions that would never be substituted by advanced automation or machine learning (ML), they have to embrace new trends in the software world — and adapt accordingly.</em></p><p>Anna Royzman, the founder of <a href="https://testmastersacademy.org/">TestMasters academy</a>, hosted Dror, TestCrafts’ CEO on our most recent webinar: <a href="https://hubs.ly/H0dQbhs0">“How manual testers should adapt to the DevOps Era”</a>. Dror discussed what has changed in the software industry since switching to Agile and DevOps, and how it affects Software Testing and QA professionals. He further explained how testers can up their game to increase their value and become essential in the modern DevOps process.</p><p>This webinar had a focus especially on ML assistance on automated testing. ML or artificial intelligence (AI) tools are the hottest topics right now in the testing industry, however, QA managers and manual testers have little to no knowledge about it (see our poll below). Therefore, Dror gave priority in lecturing the attendees on the <strong>relevance of ML assistance for a manual tester</strong> — with real examples, statistics, and applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vYuDmj1cFPgdWFnnlMiKGg.png" /></figure><p><em>Source: Poll conducted on the Webinar. There was a fourth option: “Very familiar” but none of the attendees checked this one.</em></p><p>Dror closed the webinar with a Q&amp;A with the viewers. This Q&amp;A caught us by surprise with the number of thorough questions. For your benefit, here are the answers to the questions provided:</p><p><strong>Q: The example that you gave for ML of a button moving from one side of the screen to the other — this can be addressed by having custom attributes. How can ML address such problems?</strong></p><p>A: That is true, custom attributes could be used — you can achieve that with plain Selenium but you would need vast resources to get to that level. ML, on the other hand, is a learning algorithm. If there is an element that has changed and the text failed, we ask the user for help (by pointing to the correct element on the screen) and add that to the algorithm’s body of knowledge. Next time that we are going to face this challenge, the text will fix automatically — this is how ML is being used in that sense. We do have an option today to alert the users on elements that are more probable to break because they are written in a certain way. We know that in advance by analyzing all the elements in the test and we give the user the option to select the strongest attribute to that element. Again, we add this information to the data of the algorithm to improve it going forward.</p><p><strong>Q: Does TestCraft support regression testing? Or you can you say load testing?</strong></p><p>A: Our focus is on regression testing or functional testing on web applications, not so much on load testing.</p><p><strong>Q: Is the TestCraft system 100% codeless? Absolutely no code maintenance?</strong></p><p>A: There is no code involved whatsoever. The way it works is that the user uses a visual means to create tests either by dragging and dropping elements on the screen or sort of tracking the user actions while using the application. Under the hood, we turn that into Selenium code and it’s specifically designed for testers with no coding skills. Having said that, we do give testers with coding background the option to add certain code assets to the test and run them as part of the test — but it is definitely not required. So some of our customers that are engineers might want to do more but it’s definitely designed for manual testers.</p><p><strong>Q: What you said sounds mostly as a recording tool, which is around for almost 20 years. What’s the difference between a codeless testing platform and a recording tool?</strong></p><p>A: So in general recording technology is great because it is very easy to get started and start your first test. You just record, go through the process and there you have it. But when you want to do more complex tests, you see that it is a limited technology. For instance, it does not support iframes for example. There are all sorts of limitations to the technology. But even if you were able to record a certain test, when your application is changed and is updated frequently, then you need to find ways to intervene with the recording session which is not visual. It might be easier for you, in many cases, to record again, and if there is a session with a bug it might not be able to do so. What we are doing is very different, but from the users perspective, it is almost the same. You launch the application and you go through the scenario you want to create an automated test for. You just point and click on elements on the screen during a real session with your application. What we are doing is not recording a session but collecting the single steps of the user actions using this steps in order to create a visual model of the test on a canvas. This model is built out of single steps (a click on a button, a text entry) and is very easy to maintain and edit. You can very easily remove an element, add an element, start a new branch on your test, a new scenario — so its very flexible this way. And also it supports all of the iFrames, tabs etc. that are not supported with a recorder.</p><p><strong>Q: Which platforms does TestCraft work with? iOS, Android, web?</strong></p><p>A: We support web applications for all of the common browsers (Chrome, Firefox, Internet Explorer). We also support mobile applications with mobile simulators for Android and iOS as well. We do not support native mobile apps.</p><p><strong>Q: Do you have to retrain the ML model for every new site you want to test?</strong></p><p>A: First of all the model comes fully functional out of the box. Training it only makes it better over time and this is application specific.</p><p><strong>Q: How easy is it for manual testers to adapt to ML when the world of manual testers is already struggling with BDD and TDD?</strong></p><p>A: As I mentioned before, you don’t need any coding skills to use our platform, so it is already enough if you understand the business process, the application and what needs to be tested. You don’t need any technical skills for using our tool. ML is used under the hood — It tracts your simple visual actions on the screen and these feed the algorithm and makes it better over time. So you don’t need to learn anything about it or understand how it works. It’s nothing like those other platforms where they do require some training or technical understanding (coding skills). It really is <a href="https://www.testcraft.io/">codeless</a>.</p><p><strong>Q: Tell us a little bit about the ML part of it because there are a lot of questions on that. Do you ever have to adjust the model to send it to the customer? Or is it just fine?</strong></p><p>ML is smart enough to overcome certain changes in the way the elements are being used in the application. It is not as smart as to create its own tests, so if there is a change in the logic of the application, then the tester would need to create a test for that new logic. However, if you have a regression test where the logic remains the same but the application is going through constant changes and updates, then it is smart enough to overcome most of these changes. And as I mentioned earlier, it improves over time. So the work of the tester creating automated tests is very simple — just to go through the test’s steps. Again, under the hood, we write the code for that. We allow testers to connect with their DevOps or CI/CD processes and it’s all being done automatically including the test execution, fixing broken tests, and learning from the user actions.</p><p><strong>Q: Does the test results’ output from TestCraft work with other tools, like bug reporting tools? And if so, which ones are partnered with TestCraft?</strong></p><p>A: Yes. When there is an issue or bug that is identified on the TestCraft platform, then you have different options. First of all, after every test execution, you have a set of screenshots for each of the steps of the test. If there is a bug or issue, you can share that information with the development team, for example, and they will have a very clear understanding of what went wrong. Then, you can report the bug in the TestCraft platform — so you can track it. Also, you can report it directly into Jira. You can have Jira as your issue management platform and it feeds of bugs directly from our system — which will include all of the information the developer needs in order to address it, including screenshots of the test. You can also communicate it through Slack or via an email.</p><p><strong>Q: Is this tool more for UI testing or can you code basic sets of functions and reuse them?</strong></p><p>A: There are two different answers for this question; first of all it is focused on UI. Basically what we do is end-to-end testing but through the UI. So we test the functionality of the system through the way that it is being reflected in the UI. We do have an option to also test backend components. For example, if you made a change on the UI and you want to make sure it was reflected correctly in the database, we do support that as well.</p><p>Second answer: Any process, or even a single element that is being used in the system, you can reuse them across other tests — and this is a real reuse. Let’s take the login process for example you create it once and reuse it across different tests and that is something that is changing in the application — you only have to create it once and it will immediately apply to other instances that are using this test.</p><p><strong>Q: Can the tool be used for mobile app testing?</strong></p><p>A: We are not supporting native mobile applications yet, but we are supporting hybrid applications and of course mobile web applications.</p><p><strong>Q: Can a user of this tool use designs (i.e. inVision, Sketch etc.) to create the base set of tests for a mobile app, then have the tool compare the app to the base tests to determine if designs were implemented correctly?</strong></p><p>A: We are not supporting per se but we do have our own canvas for creating a test which you can use it to create a test and we will immediately turn it into an automated test. We cannot import from external tools but we have our own very simple drag-and-drop tool for doing that.</p><p><strong>Q: Are the tests created automatically from the get-go, or do we need to define them?</strong></p><p>A: There is a lot of thought that is put into this process by the testers, so the tests are not created automatically but they are maintained automatically.</p><p><strong>Q: How many times in the last couple of months did you modify your ML algorithm by itself?</strong></p><p>A: It is being modified all the time by the data that is being fed into it. The algorithm itself is not changing but the way it works is based on previous actions.</p><p><strong>Q: Does this tool work with API testing as well?</strong></p><p>A: Not at the moment.</p><p><strong>Q: How easy it is for a CI integration? Which tools can it be integrated with?</strong></p><p>A: Very easy. It’s very well ingrained into our platform. We support all of the common ones: Jenkins, TeamCity, CircleCI, Visual Studio, Heroku, and many others.</p><p><strong>Q: Even though the recording works 99% of the time, there are still instances where the elements are hidden and require some coding, which is usually the case. In some cases, an ID will change between logins in another element that is just buried somehow and is difficult for the recording to see. Are you saying that this is never the case with TestCraft?</strong></p><p>A: I wouldn’t say never. There are so many ways to implement or to create a web application. So it would be too presumptuous for me to say never. It is a major leap when you compare this to plain Selenium implementation but it is still not 100% — so there might be cases where you would still need to intervene in the code or you would need our support to do that. And by the way, we do that for our customers — if that is the case. So it&#39;s not 100% but we are getting close.</p><p><strong>Q: In an initial effort to create those test cases, there has to be an investment — manually. How automation is better than manual testing?</strong></p><p>A: That is easy. First of all, you only have to create the tests once. And then you have a set of test cases that are automated — you can put them on a schedule and run them on multiple platforms, browsers, different work environments. And you can do that in parallel. With manual testing, you need to go through the process over and over again, across different platforms and maybe using different data sets for each of the tests. So the permutations for a single test can be very significant. When you automate a test, you can do that with a click of a button. So it’s a significant improvement in your efficiency.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/ml-manual-testers-adapt-devops-webinar/"><em>www.testcraft.io</em></a><em> on September 17, 2018, by Ely Mansur.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b27f5015eeae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/ml-how-manual-testers-should-adapt-to-the-devops-era-b27f5015eeae">ML &amp; How Manual Testers Should Adapt to the DevOps Era</a> was originally published in <a href="https://medium.com/testcraft">TestCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Better Relationships Between Developers and QA | TestCraft]]></title>
            <link>https://medium.com/testcraft/building-better-relationships-between-developers-and-qa-testcraft-4827d3b9e66f?source=rss-479e2bcb8f6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4827d3b9e66f</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Thu, 13 Sep 2018 18:33:06 GMT</pubDate>
            <atom:updated>2018-10-22T07:38:05.614Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gp-wYhEWwiRVUsT-2fz-Xw.png" /></figure><h3>Stop. Collaborate. Listen: Building Better Relationships Between Developers and QA Engineers</h3><p>The relationship between developers and QA engineers is often a work-in-progress. There are some long-lasting stereotypes on both sides that can contribute to tensions — <em>“Developers just throw the work over a wall”</em> or<em>“QA engineers block the work from getting deployed”</em>. At its core, this way of thinking is a trust issue — neither one of them is trusting that the other has good intentions in how they work and collaborate.</p><p>Creating a foundation of trust, collaboration, and communication is vital to team morale and a positive working environment. It also enhances the team’s ability to produce work that you can have confidence in because it was a joint effort — collaboration — to ensure its quality.</p><p>In my experience as a QA engineer, I’ve worked with the developers on my team to overcome these tensions and create a positive professional relationship. It’s not always easy, and it can take time to build new habits, but it’s absolutely worth the effort! Here are some of the solutions that we found for creating trust and collaboration — I think you’ll find that they can work for you, too!</p><h4>Build trust through better communication</h4><p>Improved communication goes a long way towards building a foundation of trust between developers and QA engineers, and pull requests (PR) are a great place to start.</p><p>When developers are creating a PR, we’ve generally found that it’s useful to include sections for a link to the ticket, a summary of the work, and test steps. Once you decide what’s useful to include in your workflow, make a template for it! That way the sections you need are automatically laid out, and the developer just has to fill in the relevant information.</p><p>The link for the ticket is just a nice bit for your QA engineer, so the ticket info is easily at hand for them. Summarizing the work you did gives the QA engineer some insight into the “how” and “why” around the feature work, and adds context when reviewing the actual code. Most acceptance testing or feature testing involves exploratory testing as well, but including specific test steps also help QA engineers focus on the most relevant changes. Test steps also have a side benefit for developers, by giving them another chance to review their work against acceptance criteria as they’re writing the steps. The effort that you put into creating a good PR is a way of working <em>with</em> your QA engineers, even though it’s happening asynchronously. It shows that you care enough about the work they’re doing to make sure they have what they need to do it well.</p><p>QA engineers need to make it a habit to give positive feedback on developers’ PRs. If you only comment when there’s a problem, all of your comments will start to seem problematic. Take the time to show that you’re giving meaningful attention to the developer’s work. For instance, I’ll point out a good UX solution, or show appreciation by noting where they reduced tech debt. Even a simple <em>“Looks good — verified x, y, and z”</em> counts as positive feedback, because it shows that you’re noticing what they’ve done. People often have a <a href="https://en.wikipedia.org/wiki/Negativity_bias">negativity bias</a>, so being mindful of the type of feedback you give — or are perceived to give — is especially important.</p><p>When developers and QA engineers create a pattern of positive communication, it sets a foundation for how they interact with each other and enhances your working relationships. More frequent and more mindful communication also creates an environment where it’s safe to raise concerns and give feedback, so communication can flow freely.</p><h4>Understand your QA team</h4><p>QA engineers often end up with a very hybrid role, which means they get a variety of experiences with different teams or companies. Get to know your QA engineer’s background and experience, as well as what they’re interested in learning. For instance, some people excel at detailed exploratory testing, while others may be skilled at setting up and troubleshooting <a href="https://www.testcraft.io/product/">continuous delivery</a> pipelines. Do they come from a programming background? Do they have experience with performance testing or security? Do they enjoy process creation and focusing on improving developer experience? The answer is probably “Yes, and” since a common trait among QA engineers is constant curiosity.</p><p>Along the same lines, most developers I know have a specialty or preferred area of the stack that they focus on — front-end gurus who can work magic with SASS and styling; a back-end focus with a knack for building intuitive APIs; security-minded devs who have a knack for OWASP considerations.</p><p>Knowing more about each other’s experience, areas of strength and goals for learning leads to better relationships and improved collaboration. Understanding my team’s background meant that I knew who to ask when I had a sticky front-end problem, or who to pair with when I wanted to learn more about security testing. It also gave us more context into who our colleagues were as people, which created a more empathetic mindset when we interacted with each other.</p><h4>Collaborate in the problem space — “shift left” mindset</h4><p>When trust and communication are lacking, QA engineers are often silo’ed within the development workflow. Break out of this pattern by including your QA engineers early in the process. Bring them into project discoveries, where they can make recommendations for test plans and architecting for easier testing down the line. If you’re discussing a bug or blocker, loop them into the chat — not only does it increase their context and overall awareness, but also helps QA engineers contribute to finding causes and solutions.</p><p>QA engineers can help make this shift for themselves as well. For example, when I’m working on this “<a href="https://www.testcraft.io/connecting-manual-testers-devops-webinar/">shift left” mindset</a>, I look at my team’s calendars to see what meetings I should participate in. If my team has a central source for discovery documentation, I’ll create a test plan or testing templates and add them in. I also make sure to talk about my work with my team in standup and retro, so that my work isn’t silent and therefore overlooked. If I’m adding tests to check for a bug that keeps cropping up, I mention it to the developer so they can run the tests when they’re working on it.</p><p>It takes time for people to change their habits, so be patient and keep the conversation going — remind them how being included benefits you and helps you do your job better. If you can explain it that way, instead of just wanting them to do the “extra work” of looping you in earlier, they’ll be more motivated to do it. Of course, they want their QA engineer to be supported, and if they can help you carry out your job more effectively, they will.</p><h4>Stop. Collaborate. Listen.</h4><p>I generally wouldn’t recommend taking your life advice from Robert Van Winkle; but in this case, he was onto something.</p><p>When you have improved working relationships, you have happier people who feel safe in their work and team environments. That means everyone can focus on the actual projects, instead of being blocked by poor communication and a lack of trust.</p><p>Mindful communication, consistent collaboration, and empathy for the people you work with create a strong foundation for a high-performing team. Working together, you’ll be able to increase the quality of work you produce and have a smoother development workflow from start to finish.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/building-relationship-developers-qa/"><em>www.testcraft.io</em></a><em> on September 13, 2018, by Angela Riggs.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4827d3b9e66f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/building-better-relationships-between-developers-and-qa-testcraft-4827d3b9e66f">Building Better Relationships Between Developers and QA | TestCraft</a> was originally published in <a href="https://medium.com/testcraft">TestCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>