<?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[TestCraft - Medium]]></title>
        <description><![CDATA[TestCraft — Create &amp; Run Automated Test Flows with Codeless Selenium. Agile. Simple. Reliable. - Medium]]></description>
        <link>https://medium.com/testcraft?source=rss----bb7d9cfb7d06---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>TestCraft - Medium</title>
            <link>https://medium.com/testcraft?source=rss----bb7d9cfb7d06---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:10:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/testcraft" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[TestCraft is part of Sauce Labs Technology Alliance Program]]></title>
            <link>https://medium.com/testcraft/testcraft-is-part-of-sauce-labs-technology-alliance-program-be405bb487d4?source=rss----bb7d9cfb7d06---4</link>
            <guid isPermaLink="false">https://medium.com/p/be405bb487d4</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Wed, 20 Feb 2019 09:30:49 GMT</pubDate>
            <atom:updated>2018-07-29T08:16:03.729Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5tYVDfxaju2F1RBPekhUA.png" /></figure><p>We are happy to be part of the new <a href="https://saucelabs.com/news/sauce-labs-launches-technology-alliance-partner-program">Sauce Labs Technology Alliance Partner (TAP) program</a>. As part of the program, TestCraft collaborates to create compelling integration with the Sauce Labs Continuous Testing Cloud. With this new program, Sauce Labs’ customers will enjoy an integration that extends the continuous testing capabilities deeper into a customer’s software developer pipeline.</p><p>The <a href="https://saucelabs.com/blog/sauce-labs-announces-new-technology-alliance-program-">Sauce Labs TAP program</a> provides customers with numerous benefits. First, it makes it easier for them to integrate and use Sauce Labs platform more effectively. It also eases the access to TestCraft’s codeless Selenium test automation platform and other industry-leading solutions that work seamlessly with Sauce Labs. Last, it ensures improved performance and usability between Sauce Labs and other development tools.</p><p>The Sauce Labs TAP program initially focuses on five partner categories:</p><p><em>“TestCraft is proud to be chosen for the Test Authoring category as part of the Sauce Labs TAP program. This fits our strategy to enable a smooth end-to-end testing experience while integrating with the industries leading platforms”</em> says Merav Zaks, TestCraft’s VP of Marketing.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/testcraft-sauce-labs/"><em>www.testcraft.io</em></a><em> on July 23, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be405bb487d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/testcraft-is-part-of-sauce-labs-technology-alliance-program-be405bb487d4">TestCraft is part of Sauce Labs Technology Alliance Program</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[Shifting Left: How to Manage Your Open Source Components]]></title>
            <link>https://medium.com/testcraft/shifting-left-how-to-manage-your-open-source-components-4b00638d2db?source=rss----bb7d9cfb7d06---4</link>
            <guid isPermaLink="false">https://medium.com/p/4b00638d2db</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Wed, 20 Feb 2019 09:30:37 GMT</pubDate>
            <atom:updated>2018-07-30T08:23:05.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fXQYCLQtNLQBpKTEdAo0GQ.png" /></figure><p>A guest post by our sister company <a href="https://www.whitesourcesoftware.com/">WhiteSource</a> — a leader in the app security testing space.</p><p>Pushing solid products through the software development lifecycle while ensuring the highest quality standards can be a serious challenge for teams of any size. There is a great deal of value in using tools to automate our QA processes, cutting time at the end of the process, and picking up on those pesky bugs before the product makes it way out the door.</p><p>We understand all the advantages of the use of an <a href="http://www.testcraft.io/">automation test platform</a>. However, we must take a step back to recognize there are opportunities to catch issues and vulnerabilities before they reach the QA step. We can do this by essentially shifting left our security checks to the earliest stages of the software development lifecycle (SDLC). Then, as you hit the QA stage it is imperative to continue shifting left. Your testing team can perform this by starting to test early in the SDLC.</p><p>Most of us are already familiar with the need to use tools like Static Application Security Testing (SAST) tools to check our proprietary code for potential vulnerabilities, but that only covers a piece of the pie.</p><p>Open source components comprise between 60–80% of the code base in modern applications. They contain the libraries and frameworks that are written and maintained by the open source community and are available for reuse by others in line with the licenses. Developers rely on open source without giving it a second thought because it’s cost-effective and efficient, helping them speed up the DevOps lifecycle. Open source also allows them to give their organization’s proprietary codes that extra bit of strength that they need to stand out in today’s marketplace without needing to reinvent the wheel for every single feature.</p><p>As this practice continues to grow, it’s important to pause and take a closer look at the processes and tools that we use when we work with open source software. Open source components are not like a proprietary code in how they are written and maintained, and therefore require a different kind of management. They present a challenge that must be managed using different tools which work according to other rules.</p><p>Every developer knows that open source components are ready and waiting for download on a number of online repositories like <a href="https://github.com/">GitHub</a> or <a href="https://search.maven.org/">Maven Central</a>, but how many developers know the quality, security, or compliance levels of the open source code that they are using? Leaving those issues unattended in the early stages of production could end up costing much more when a product is already nearing its release.</p><h4>Your open source security won’t manage itself</h4><p>Security-wise, managing open source security could turn into a full-time job if you’re not familiar with the<a href="https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar"> open source bazaar</a>, sometimes lovingly referred to as the Wild West. Once discovered, open source vulnerabilities can be published across a number of security advisories and databases, rather than in one centralized location. Keeping track of all those known open source vulnerabilities is nearly impossible to carry out manually, especially at a large scale.</p><p>The next step is locating the patch, fix, or updated version for remediating the security vulnerability, and that too can turn into an endless task. That leaves us with one last, but in no way small, a task of combing through our code base for dependencies between vulnerable open source components and libraries.</p><p>When a security vulnerability is made public, it’s hunting season for hackers. That means we need to locate the risky open source component and all of its active dependencies as quickly as possible if we want to stay one step ahead of the exploits. Manual labor simply won’t cut it.</p><h4>Automate your way through the open source bazaar</h4><p>The only way to successfully ensure that you’re using open source without risking your company or your customer’s safety is to implement a <a href="https://resources.whitesourcesoftware.com/devops/3-key-considerations-for-devops-automation">DevSecOps</a> approach to your open source management policy. Specifically,<a href="https://www.whitesourcesoftware.com/how-does-it-work/"> automating the open source management process</a> from the earliest stages of the product lifecycle.</p><p>Using a Software Composition Analysis (SCA) tool that can automatically and continuously track your project’s open source components will save you, your stakeholders, and your team a lot of time and money as you race to release a new product or version.</p><p>An automated SCA tool will do the tedious heavy lifting, continuously tracking open source components in your code, matching them with an up-to-date database of open source vulnerabilities and fixes. The tool runs throughout the software development lifecycle, alerting admins when a vulnerable open source component is found, or even breaking the build to ensure a project’s safety, should a developer attempt to commit a vulnerable component hen provides actionable remediation suggestions for those pesky vulnerable components.</p><h4>Stay calm and automate your open source management continuously</h4><p>Open source gives us great opportunities to boost the pace of development, and focus on producing innovative products that make our customers happy in today’s competitive marketplace.</p><p>In order to stay on top of our game, we can’t ignore the fact that open source components require a different set of processes and tools than proprietary software. Investing in DevSecOps tools and policies without addressing the risks of open source components will only take us so far. If we really want to harness the power of open source, we need to manage it.</p><p>The best way to ensure we are one step ahead of the hackers and out of courtrooms without missing a beat is to incorporate automated tools that continuously track our open source usage and match them up against the most current data about open source components, their vulnerabilities, risks, fixes, and updates.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/shifting-left-manage-open-source/"><em>www.testcraft.io</em></a><em> on July 19, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b00638d2db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/shifting-left-how-to-manage-your-open-source-components-4b00638d2db">Shifting Left: How to Manage Your Open Source Components</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----bb7d9cfb7d06---4</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>Wed, 20 Feb 2019 09:30:21 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>
        <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----bb7d9cfb7d06---4</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>Wed, 20 Feb 2019 09:30:03 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[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----bb7d9cfb7d06---4</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>Wed, 20 Feb 2019 09:29:02 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[Testing in Production: It’s Time]]></title>
            <link>https://medium.com/testcraft/testing-in-production-its-time-66f1c96dad36?source=rss----bb7d9cfb7d06---4</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>Wed, 20 Feb 2019 09:25:00 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[Continuous Testing with Hands-Free Automated Page Rendering Validation]]></title>
            <link>https://medium.com/testcraft/continuous-testing-with-hands-free-automated-page-rendering-validation-d50c97f1a327?source=rss----bb7d9cfb7d06---4</link>
            <guid isPermaLink="false">https://medium.com/p/d50c97f1a327</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 11:45:26 GMT</pubDate>
            <atom:updated>2018-06-26T09:52:30.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-B0IeUCuNAOhreuZ-76JQ.png" /></figure><h4>Motivation</h4><p>You’re a developer, just finished the last release test yesterday and deployed to production. When you wake up the next day, there are 12 unanswered calls, 3 voicemails, and about 50 emails. Something about the page while in production was completely messed up and unreadable.</p><p>When you take a look, that’s actually the case, the entire site is completely messed up. You instantly panic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*KeZdplPXd9TrcMZSCkO8Bw.png" /></figure><p><em>Figure 1: Example YouTube page without CSS</em></p><p>OK, breath, let’s think. Why did this happen? You believed to have tested everything. This makes no sense.</p><p>Wait, you forgot to deploy the CSS. Let’s do that quickly.</p><p>Could this have been avoided? The answer is YES! It is very easy to avoid this situation with simple page rendering validation checks, that can be added to any functional test.</p><h4>Does visual validation help teams execute?</h4><p>Yes, definitely. Imagine an engine that conducts a smart (more on that later) continuous full page validation for every functional test flow, behind the scenes. Why is this important?</p><ul><li>Agility and developer productivity: Developers do not want to spend more time testing. Team leads want developers to develop, but they also want to avoid disasters. Executing visual validation on top of functional tests tells developers within minutes of code committed errors. Developers don’t need to remember what they did in order to undo a lot of their code. This is because the defect was found within minutes.</li><li>Efficient cross-screen and <a href="https://www.testcraft.io/run-edit-tests-live-internet-explorer/">cross-browser</a> rendering validation: Like it or not, the page has to look good on all screens. Instead of repeating test flows for rendering validation, you can efficiently validate rendering in the background on all screens. Great efficiencies can be achieved because many of those experiences leverage the same HTML5 code base.</li><li>Complementary to functional testing: In a typical functional test flow, only a few elements are actually interacted with. For example, in the login page, the flow would interact with the username and password text fields and then click the login button. A full-page visual validation would scan the entire page in one shot. Although it’s not a functional scan of each element, it is at least validates that the key elements are still there (or not).</li></ul><h4>Visual validation solution considerations</h4><p>There are many commercial and open source solutions one can use, some paid, such as <a href="http://www.applitools.com/">Applitools</a>, others are open source, such as <a href="http://galenframework.com/">Galen</a>, <a href="https://github.com/wswebcreation/protractor-image-comparison">image comparison for Protractor</a> etc.</p><p>How would you differentiate between those? There are many aspects to this, I will describe the top considerations:</p><ul><li>Alignment to your toolset: How much effort it would take to integrate the solution? For example, <a href="http://www.testcraft.io/">TestCraft</a> is pre-integrated with Applitools, making it super easy to implement image comparison. Applitools is easily integrated (few lines) with any scripting language and tool. Open source tools are mostly language-unique, for example, the Protractor image comparison is unique to Protractor/Javascript.</li><li>CI integration: Are you able to gain insight into visual changes (suggesting potential defect) quickly, with scaling CI builds? Is it possible to integrate to common CI tools such as collaboration tools (ex: Slack), defect management (Jira) etc.? Here, for example, Applitools has a nice Jira integration to report a defect. The tool also offers the ability to comment on failures, encouraging developers to interact inside the tool.</li><li>Different ways to create screenshots: Element screenshot, viewport screenshot, and full-page screenshot (viewport+ scrolling). This is very useful since an element screenshot can be used to isolate the comparison (from the rest of the page), reducing noise. Another benefit is when the page is built of components and you want to modularize your test. A full-page screenshot would be more appropriate for the traditional full-page rendering validation (for designers and marketers).</li><li>How is the image analysis managed? This answer comes in two aspects:</li><li>The algorithm itself: the scan method, and what tolerance threshold methods are available, ignore colors, antialiasing etc.</li><li>The scan policy: this is one of the most important points. In many web pages there will be rotating content, content will change on a daily or hourly basis, perhaps advertising etc. The image scanning policy should allow defining “areas” where you may want to validate on a pixel-perfect policy. Other areas, for example, those presenting ads with rapidly changing content, you may want to block out. A good tool would allow you to block out multiple regions from a screenshot.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*Uh0PAs7XVyQBq3HRJnoX9A.png" /></figure><p><em>Figure 2: Example full page comparison result. Note the difference in Google search timing is highlighted</em></p><ul><li>Clear view and actionable dashboard/working environment: Is the reporting built in such way that it’s clear to quickly determine the issue when there’s a lot of tests running? Also, can you quickly mark a baseline, can you define a policy for an area etc.? Take a look at <a href="http://www.applitools.com/">Appitools’ dashboard</a>/work area to get a reference.</li><li>Pricing model/support: Of course, there’s the issue of cost. Some tools are paid, free-to-pay, and open source. For example, Applitools has a freemium option, and then a paid version. Galen and others are open source, but this means that you cannot enjoy a premium support service from a vendor. The community around the open source solution might do a nice job, depending on your urgency, but it’s not guaranteed. Open source solutions also require ongoing hosting cost, not to mention building the assets that are needed, such as dashboards, integrations etc.</li></ul><h4>Embed visual validations into your process</h4><p>Hopefully, this brief view of visual validation tools offers some insight into what can be achieved in a fairly low effort. I highly recommend trying it out on one of your next projects: Integrate the tool of choice, establish a baseline for the pages you want to scan, and from there on, let it run in the background. I believe you will find the defects found in this approach will not only offer you a new layer of coverage for “almost free”, but it would also make the marketing folks super happy.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/continuous-testing-automated-page-validation/"><em>www.testcraft.io</em></a><em> on June 21, 2018 by Amir Rozenberg.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d50c97f1a327" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/continuous-testing-with-hands-free-automated-page-rendering-validation-d50c97f1a327">Continuous Testing with Hands-Free Automated Page Rendering Validation</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[How to Become Better at Test Automation — Webinar]]></title>
            <link>https://medium.com/testcraft/how-to-become-better-at-test-automation-webinar-9547b7d1727?source=rss----bb7d9cfb7d06---4</link>
            <guid isPermaLink="false">https://medium.com/p/9547b7d1727</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 11:45:04 GMT</pubDate>
            <atom:updated>2018-07-15T09:03:46.355Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOG3oQVq4oC2KUF0Q2QOmw.png" /></figure><p>We at TestCraft, a codeless automation testing platform, were lucky enough to host Bas Dijkstra, a leading test automation consultant, in our most recent webinar, “How to Become Better at Test Automation”.</p><p>In the webinar, Bas shares his beliefs on how test automation should be done right and what were the mistakes he had done at the beginning of his career. Bas believes that companies and automation testers should focus on the “why” rather than the “how”. We share the same belief and therefore decided to summarize the webinar for our community’s convenience. In this short blog post, we will bring you the highlights of Bas’s webinar.</p><h4>Start with the Why</h4><p>At the beginning of his career, Bas thought he knew it all about automation, only now did he realize he was far behind. He discussed in the webinar a couple of instances in his early career days where he only focused on the specific tools they used for automation. Now, he sees that automation engineers today are making the same mistakes and falling into the same traps as he once did. He comes across many questions from testers on Quora and Linkedin asking, which tools they should use and how to implement a code to a certain platform. No one seems to start with the <strong>why </strong>or <strong>what</strong> — The ‘why’ is the need for automation and the ‘what’ is what are you going to automate.</p><p>Bas explains that it is imperative to understand the purpose clearly as to why you need to apply a certain <a href="https://www.testcraft.io/product">tool to your automation strategy</a>. The question is, where do you start if you want to improve your automation testing capabilities?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*_jOpZJXNANHfmZCM5Y2mZQ.png" /></figure><p><em>How do you become a better automation engineer?</em></p><h4>“We don’t need more automation engineers. We need better ones”</h4><p>The first step to solving this question is the training implementation. Bas has stumbled upon many training curriculums that only discuss how to implement automation in a specific tool or set, for example, ‘Essential Selenium’, ‘Introduction to Cucumber’, etc. Tool-centric training should be avoided because you will miss the important underlying patterns and principles. An example of something that isn’t normally taught in a traditional training program is if there is a case where you must go through the same sequences of user interface screens or pages with many different sets of inputs and outputs parameter. This is a sign you might want to skip UI and instead verify business logic through an API or unit test. The training needs to be focused on how to build an automation strategy and how to manage certain expectations around automation. Another focus should be on when not to automate, as well.</p><p>The perfect automation training according to Bas starts with software testing, it’s the way to effectively move towards automation. <a href="https://www.testcraft.io/selenium-testing-ebook/">Automation awareness</a> is just simply to learn all you can about automation. Learn what automation can or can’t do and plan it in your daily software testing framework. Patterns and principles are independent of most of the tools. It would be smart to learn the patterns, this will lead you to easily pick up the knowledge for another tool.</p><h4>Patterns and principles over tools and technique</h4><p>Bas ended off the webinar with the advice of how to make the automation space better. He constantly reminds us to not only focus on tools alone. Like him, you should share your experiences and mistakes to the community so everyone can learn from each other. Start seeing automation for what it is — <strong>Automation is not the end goal.</strong> It will help make your software testing more productive and actively better, but it’s not the ‘holy grail’. Last but not least, answer the <strong>why </strong>while facing an automation task.</p><h4>An automated codeless solution</h4><p>Like Bas, we at TestCraft, believe that testers should be professionals in testing — they should know what to test and know the business itself inside and out. As Bas mentions, only after they know the ‘what’ and ‘why’ should they deal with the ‘how’.</p><p>That is the reason why we created our platform — to enable any tester to turn their test scenarios into automated ones, without coding. We believe they should focus on the test scenarios themselves, rather than the actual code. We also take care of the maintenance issues, so they can focus on the ‘what’ and ‘why’.</p><p>If you like to hear more on the subject feel free to sign up to watch the <a href="https://hubs.ly/H0cSnr80">recorded webinar here</a>.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/become-better-test-automation-webinar/"><em>www.testcraft.io</em></a><em> on July 5, 2018, by Lauren Mueller.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9547b7d1727" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/how-to-become-better-at-test-automation-webinar-9547b7d1727">How to Become Better at Test Automation — Webinar</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[“Connecting Manual Testers to the DevOps Era” — Webinar]]></title>
            <link>https://medium.com/testcraft/connecting-manual-testers-to-the-devops-era-webinar-b18aa9a44247?source=rss----bb7d9cfb7d06---4</link>
            <guid isPermaLink="false">https://medium.com/p/b18aa9a44247</guid>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 11:44:47 GMT</pubDate>
            <atom:updated>2018-07-15T09:05:02.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6W8afzxqsjThyBov4aY8qg.jpeg" /></figure><h3>“Connecting Manual Testers to the DevOps Era” — Webinar presented by Dror Todress hosted on SoftwareTestPro</h3><p>Recently Dror Todress, our CEO was invited by <a href="https://www.softwaretestpro.com/">SoftwareTestPro</a> to discuss his thoughts on<a href="https://www.youtube.com/watch?v=hMykuHD6coo&amp;feature=youtu.be"> how we can connect manual testers to the DevOps era</a>. Dror examined why and how software testing was left behind in the agile sprint. He also goes on to mention new automation methods. Dror was approached, during and after the webinar, with many questions relating to our platform. We thought it would be considerate to share them with you here.</p><h4>Shifting left toward DevOps</h4><p>Now more than ever there is an eternal need to introduce new software versions and continuous updates into the release cycle. It is important for development teams to adapt to these new processes. Development is a core activity of any software company and the constant changes to its methodology requires attention and teamwork within the organization.</p><h4>A manual tester’s task in the move to agile</h4><p>Dror Todress sat down to touch on the point that testing seemed to be left behind during the shift to agile. Manual testers were faced with an impossible task of keeping up with the agile pace while using outdated tools. Dror mentions that test automation is a must to connect manual testers to the DevOps era. Automation has proven itself as the main method for planning and building an automation framework.</p><h4>The codeless automated solution</h4><p>Unfortunately, automation comes with many bottlenecks. A couple of big burdens are the maintenance issues and code behind certain frameworks. That’s why Dror mentions a new codeless automation methods that solve these issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KF1ZU0ySS0tdN3NYu13ekw.png" /></figure><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>Is Your platform HIPAA compliant? Do you have current healthcare clients in the USA?</strong> <em>Not at the moment. However, we are ISO27001 certified and we leverage the security measures offered by Amazon AWS.</em></p><p><strong>Can you help me understand how you distinguish between “manual tester” and “tester”? Is a “manual tester” someone who doesn’t use tools? …or a tester who doesn’t write code?</strong> <em>I’m mostly referring to testers that don’t write code. They do use tools for test management, issue management, and test specification but not for test automation.</em></p><p><strong>How do you access applications your clients want to test? Do your systems have direct access to internal company servers?</strong> <em>Our solution runs in the Cloud. The way it works is that for every test execution we spin up a dedicated server on our Amazon platform — on this server we launch specific browsers and use this remote browser to navigate and access the testing application. In order to allow a secure access to internal servers, our customers can simply whitelist our IP on their own firewall. Alternatively, we offer a virtual private cloud on Amazon that allows customers to have their own separate test environment for execution as part of our platform and create a VPN tunnel between the virtual private cloud and the customer network. The latter option is considered more secure and satisfies customers in highly regulated industries, such as banking, insurance, financial services etc. We also have an on-prem version where everything runs in the customer’s network, but in this case, the customer loses some of the benefits of using a SaaS platform.</em></p><p><strong>It seems like your tool is customized — how can we do coding? Which languages does it support?</strong> <em>We are targeting mostly manual testers and don’t require any coding skills. However, we do allow our customers to write javascript code and execute it as part of a test on our platform. We also offer “</em><a href="https://www.testcraft.io/selenium-bricks/"><em>Selenium Bricks</em></a><em>” that enables the import of Selenium libraries into our platform and make them accessible to the manual tester through the same interface.</em></p><p><strong>How long is the free trial?</strong> <em>The trial lasts 3 days with an option to extend it if necessary. We kicked off the trial with a discussion about customer infrastructure and testing requirements. We then set the success criteria for the trial with the customer and continue with a short training session. The customers then continue on their own with our support as needed. We assign each customer with a dedicated success manager to make sure they deliver results.</em></p><p><strong>How do you get around challenges with the application when some parts of it don’t interact with automation tools?</strong> <em>Some tools are not sufficient… Our focus is on supporting web applications on different platforms — this means desktop browsers, of course, but also mobile browsers. We allow customers to write code although we are targeting manual testers. If a customer has coding skills or an engineering team they will be able to write javascript code and can have their testers use that code as part of the test. If there’s an area of the tested application that isn’t supported natively by our platform, adding code assets might help. In addition, Selenium Bricks allows us to import existing Selenium libraries that might offer certain features that aren’t natively available on our platform. We then make the Selenium Bricks accessible through our platform to testers using the same visual UI. So in short, either import Selenium libraries or you can use your own code and apply it on our visual test platform.</em></p><p><strong>Can we configure TestCraft with different tools such as HP QC, Microsoft TFS, etc.? JIRA?</strong> <em>We do support JIRA for ticketing, Jenkins, TeamCity, Travis, Circle Codechips and, Microsoft Visual Studio for execution triggering. We also support test management solutions such as PractiTest.</em></p><p><strong>Who will define elements in TestCraft and how will TestCraft detect these elements?</strong> <em>Our platform natively supports the vast majority of elements and actions that might be available on a web application. The platforms </em>identifies<em> the elements automatically as the user is creating tests.</em></p><p><strong>Are BDD test cases supported?</strong> <em>No, our platform is </em>visual<em> based, rather than BDD based. We believe it’s easier for testers without coding skills to build their test scenarios visually.</em></p><p><strong>Could you explain the codeless strategy once again?</strong> <em>Sure. Our platform is built as a layer on top of Selenium. Automated test scenarios can be created in one of two ways, but does not require coding knowledge. We then translate those test scenarios into Selenium code. The first way is by a simple drag and drop of test steps on a canvas to create test scenarios. This way enables testers to create test scenarios even before the code is ready (“shift left”). The second way is creating the test scenarios in a “live” mode while the app is running, by simply going through the scenarios. It may appear as a “record replay” solution, but in fact, we’re creating a model and not a recording which can be adapted to changes. The codeless strategy is also relevant to maintenance — a great pain point in code-based test automation. We use AI technology that automatically overcomes most changes in the app (more than 80%). If a test does break eventually (“the other 20%), fixing it is very simple — you don’t need to look for the error in the code, fix it and deploy all over again — you just point and click on the correct element to fix it.</em></p><p><strong>Is there support for codeless Mobile testing and Rest API testing?</strong> <em>We support mobile web testing and have different mobile simulators to run the tests on. We do not currently support native mobile apps. We can incorporate Rest API calls within test scenarios, however, it is not a pure API testing tool.</em></p><p><strong>How can you convince a company who is using Selenium to use TestCraft?</strong> <em>We believe that there are many advantages of using TestCraft, even for those that </em>do<em> not begin automation from scratch and are already using Selenium. </em>The first<em> advantage is maintenance. TestCraft dramatically reduces maintenance overhead — using AI technology, we automatically overcome 81% of the changes in the app, most of which would break tests in plain Selenium. In the event of a broken test, fixing it in TestCraft takes a fraction of the time it would take using plain Selenium. It doesn’t require finding the error in the code, fixing it and deploy all over again. Instead, we will point out where the error occurred, and the tester would then need to simply point and click to fix it. </em>The second<em> advantage is the ease and speed of building new test scenarios in TestCraft vs. plain Selenium. </em>The third<em> advantage is the reusability of test elements which makes the whole automation process much more productive and maintainable. The fou</em>rth<em> advantage is the ability to run tests within the TestCraft platform, on different browsers and work environment, without the need to maintain such grids or pay for external test labs. </em>The fifth<em> advantage is “Selenium Bricks” which enables our customers to easily import Selenium libraries created by the Selenium community into the platform.</em></p><p><strong>Can we use TestCraft to test Hybrid Mobile Apps?</strong> <em>Yes</em>.</p><p><strong>Does TestCraft use Selenium in the background?</strong> <em>Yes, </em><a href="https://www.testcraft.io/"><em>Selenium is at the core of our platform</em></a><em>. You can think of our platform as a layer on top of Selenium that allows Selenium to become more accessible to business and manual testers. We are working hard to deliver more of what the Selenium community has to offer using our Selenium Bricks technology, mentioned previously.</em></p><p><strong>How well does the AI handle dynamic data sets, i.e. e-commerce ticketing platforms where specific performance and seat availability will change frequently? Is it able to accommodate for these situations automatically?</strong> <em>Yes, it does. This is part of what the AI algorithm is accomplishing. It’s there to analyze such dynamic changes and fix the test accordingly, without user intervention.</em></p><p><strong>Can your solution work on MAM wrapped applications?</strong> <em>It depends — if it’s mobile web apps then yes.</em></p><p><strong>How would your automation be executed, using what tools (Jenkins)? Any integration with Jenkins, JIRA, Slack?</strong> <em>We have integrations with all the tools you’ve mentioned — you can run the tests and receive their results from any CI/CD tool, including Jenkins. You can open issues in Jira and receive system notifications on Slack. We also integrate with Test Management tools and with Applitools.</em></p><p><strong>How do you manage “motivation” to move a manual tester to be an automation tester?</strong> <a href="https://www.testcraft.io/manual-testing-dying-quote-hit-nerve/"><em>Manual testers bring a lot of value to an organization</em></a><em>. They are very knowledgeable about the business processes and applications, but in some </em>cases,<em> they are concerned about the future. We see some companies trying to take manual testers and turn them into software engineers. I believe it might defeat the purpose as there is no guarantee they will become good engineers after taking coding courses. With a codeless platform they can move to the next level of becoming great automation engineers — they would leverage their knowledge and experience to create excellent, resilient automated tests.</em></p><p><strong>What is the verification/review process available to confirm differences that the machine learning process fixes are correct and valid?</strong> <em>There is a fine threshold over which we break the test and ask for the user to point to the correct element. Our sophisticated set of AI algorithms is able to ascertain what that threshold should be in order to assure there are (almost) no false </em>positives<em> while keeping the number of broken tests to a minimum. So, the verification process you have asked about is done automatically by the platform itself with great success.</em></p><p><strong>How do you decide what to automate first? Defects or functional tests?</strong> <em>It depends. We don’t do the automation ourselves. We allow our users to automate on their own. I would say you should start with functional testing — but it depends on the specific tester and application.</em></p><p><strong>Can this tool talk to Defect Management Tools?</strong> <em>Yes, we are integrated with Jira. If you are using a different tool — we can integrate with it as well. See answer number 18 for more info.</em></p><p><strong>Is there any functionality in Selenium that is not in TestCraft?</strong><em> I’m sure there is. Selenium has a vibrant community around it that keeps adding new functionality to it. We can make new functionality available with our recently announced Selenium Bricks technology — it allows you to take any Selenium library and make it accessible to manual testers through our platform. If a customer has a specific need that is currently not supported we will work with them to identify and implement the right Selenium Brick. We foresee a marketplace for Selenium Bricks being developed with time.</em></p><p><strong>Can the test scripts be kept in the internal company repository for proper versioning? (We use a very strict instance of Gigiscloud)</strong> <em>At the moment no. Just to explain how it works — we do have a versioning option on our platform so you can manage branches and versions but you can’t integrate with external Git platforms or other version management tools. We do however allow a customer to download the Selenium code that is generated by our platform which is very important for continuity — if any of our customers </em>decide<em> to step away from our platform for some reason, they can rest </em>assure<em> that their investment won’t go to waste. It’s not our intention to lose them but, this is something we offer that is unique.</em></p><p><strong>The new automation tester only records the scripts? Do you only use Selenium RC?</strong> We aren’t recording the script, recorders, in general,<em> are limited. We offer the user experience of a recording, so our users can go through an application and point-and-click to elements on the screen and have them captured as single actions. We then build those single elements into a model on a virtual canvas that can be very easily edited and maintained.</em></p><p><strong>Does your platform have API testing capabilities?</strong> <em>Not at the moment. This is something we are working on right now.</em></p><p><strong>Does the platform integrate with continuous software development platforms like Jenkins/TFS?</strong> <em>If so, what platforms do you support? Yes, we support many different CI platforms and if we are missing one we can easily add it. We have integrations with Jenkins, TeamCity, Travis, Circle Codechips and Microsoft Visual Studio.</em></p><p><strong>Does the tool support desktop applications and Sabre (blue screen)?</strong> <em>No</em></p><p><strong>What skills should a manual tester possess in order to use TestCraft?</strong> <em>We believe that testers should know the app they are testing inside and out and learn as much as possible about testing techniques. We don’t believe that knowing how to work with a specific tool/ technology is important.</em></p><p><strong>Some testers have compared TestCraft to record and playback. Please respond to this view.</strong> <em>TestCraft can be sometimes mistaken for a record-replay because of its ease of use and because the “live” way of creating test scenarios (while the app is running) may appear similar to record-replay. However, it is completely different because: First, we create a model, not a recording. In case the app changed there is no need to record all over again, from scratch. All you need to do is simply add/delete or bind the changed element by a simple click. In most cases, you won’t even need to do that, as our AI technology will automatically overcome the changes in the app. Second, we have our own internal lab which you can use to run the tests on different browsers and work environments and upon </em>schedule<em>. Third, our visual way of creating test scenarios enables testers to create test scenarios even before the app is ready — shift left. You can start testing earlier in the dev process which will lead to major savings and increase productivity — you can’t do that with a recording.</em></p><p><strong>The biggest problem with Selenium is when programmers change the name or ID of an element. How does TestCraft handle this problem?</strong> <em>Our sophisticated </em><a href="https://www.testcraft.io/smart-binding-algorithm/"><em>AI algorithms</em></a><em> identify such changes and by “considering” many different attributes, both technical and contextual, are able to fix such tests automatically without breaking (for most changes to elements).</em></p><p><strong>What are you using for multi-platform validation? What are you running the mobile OS on (simulation or actual devices?)</strong><em> We have our own</em><a href="https://www.testcraft.io/run-edit-tests-live-internet-explorer/"><em> browser lab</em></a><em> that supports the common browsers such as Chrome, </em>FireFox,<em> and Internet Explorer as well as mobile simulators. We integrate with external lab solutions and allow customers to execute test from our platform on such labs, which include real mobile devices.</em></p><p><strong>What does your reporting look like?</strong> <em>We have a dashboard that displays information about the state of testing in an organization this includes, number of tests, execution details, information about test creation and execution, etc. This will allow you to drill down to a specific project or user level. All of the executions are being stored and will allow customers to browse through them. The results of every execution will include every type of platform execution it’s working on, details on each of the flows in a suite, if there is a success or a failure, and screenshots of every step of the way. This information can also be exported to external tools such as CI platforms, test management platforms, etc. This is how we become an integral part of the CI and DevOps model.</em></p><p><strong>Could you automate 100% of an app?</strong> <em>You can, but we don’t believe it’s good testing. You are welcome to watch our webinar about “</em><a href="https://www.testcraft.io/how-to-become-better-at-test-automation/"><em>How to become better at test automation</em></a><em>” to better understand why and how automation should be done.</em></p><p><em>Originally published at </em><a href="https://www.testcraft.io/connecting-manual-testers-devops-webinar/"><em>www.testcraft.io</em></a><em> on July 9, 2018, by Lauren Mueller.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b18aa9a44247" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/connecting-manual-testers-to-the-devops-era-webinar-b18aa9a44247">“Connecting Manual Testers to the DevOps Era” — Webinar</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[How Does Codeless Testing Drive Squad Velocity?]]></title>
            <link>https://medium.com/testcraft/how-does-codeless-testing-drive-squad-velocity-2d01043facf7?source=rss----bb7d9cfb7d06---4</link>
            <guid isPermaLink="false">https://medium.com/p/2d01043facf7</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Lauren Mueller]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 11:44:24 GMT</pubDate>
            <atom:updated>2018-07-23T10:43:04.493Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5oEHwD0thK5dD2FaxWStrg.png" /></figure><p>Have you ever wasted away a weekend due to maintenance issues? Imagine the sprint is just about to end. Devs has done their checks and launches code freeze phase, manual testing initiates, next sprint planning starts. Some test automation is available, but with over a 50% failure rate, it’s ignored. Maintaining the scripts has been a job in itself. Midway through stabilization week, a bug is found. The in-app payment feature we’ve introduced a few sprints ago was touched by someone this sprint. Problem is, that someone is off surfing on their vacation week. You will need to find the root cause, undo the code that’s been written this sprint, and redo it the right way. Here goes your weekend.</p><p>Truth be told this whole situation can be avoided. The question is, how?</p><h4>Delivering high quality in time — the codeless way</h4><p><a href="https://www.testcraft.io/">Codeless</a> comes to solve one of the main challenges of delivering high quality in time: the need to maintain complex automation scripts and endless object repositories. This could very well be a full-time job, or even a few full-time jobs, who need to invest time in making sure test automation works across all apps you create.</p><p>Take an object repository for example. More than a few items will change with every build, which can even be a few times a day. How can you ensure your script interacts with the right objects? One approach is to have the developer tell the tester all object changes in each build. That’s unlikely. Another approach is to scan the object attributes and realign the object repository before each regression test. That’s a heavy manual effort that should happen a few times a day. Last, the tester might run ‘white box’ testing. That means the tester has access to the source code of the app (again, unlikely), and no system level control is needed.</p><p>The idea behind codeless testing is that the solution itself creates and maintains the necessary user flows and object attributes without any human intervention. No maintenance is needed over time. TestCraft’s data shows that their <a href="https://www.testcraft.io/smart-binding-algorithm/">AI technology</a> can overcome more than 82% of the changes so the tests won’t break. In case a test does break, the issue will be pointed out and the fix is done by a simple point-and-click.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*--RN2iRPj1drQQN28tDp3Q.png" /></figure><p><em>Figure 1: Smart binding technology can maintain object mapping through changes in the app</em></p><h4>Building trust and value to drive adoption</h4><p>The transition from the current state of manual testing, or flaky test automation, into high coverage of codeless testing, does not happen overnight. It needs to be planned to build and optimize developer trust that the outcome is genuine and worth using.</p><p>When building your test strategy, here are some best practices to ensure validity and value:</p><ol><li><strong>Start small</strong>, prove value and increment iteratively: define a few tests flows, build them and ensure they are solid through all platforms and many iterations, and only then demonstrate those to developers. When a developer believes a failure is a real failure, the trust will grow.</li><li>Build it in a modular and reusable fashion: building the script in a smart way will minimize your chances for bugs. Further, since you can reuse test steps and test scenarios, if the app changes materially, you will know exactly which area of the script to change and you need to make the change only once.</li><li>Review the reporting: does it deliver a clear error message and the needed data for developers?</li></ol><p>Introduction of insightful, stable test automation for developers (without asking them to invest their time in creating it) would create significant collaboration with them.</p><h4>How do codeless automation testing tools help team velocity</h4><p>Coming back to our squad that’s delivering the next build. Imagine, on initiation of the sprint, new user flows are being created and maintained throughout the sprint. Those new flows need to be described once, and that can be done by anyone: there is no need for advanced or any coding skills. Imagine leveraging all of your manual testers, perhaps interns, or marketing folks to create those acceptance flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*boH55pTXcgQWtyTEcmxMCw.png" /></figure><p><em>Figure 2: Initial visual user flow generation can be done by team members who do not necessarily have coding skills</em></p><p>The real beauty comes when the developer checks in code: Automatically and without any human intervention, the code would be built, uploaded to devices and servers, and those test flows would execute on the target platforms. Notice, no human hand was required to modify the test code to adopt new object identifiers.</p><p>The developer can gain insight into defects they introduced 5 minutes earlier. They can go ahead and fix it on the spot, even faster than opening a bug in Jira!</p><p>In this fashion, teams can achieve a high-quality build in high confidence throughout the sprint and at the end of it, with no additional effort. And certainly no yelling!</p><h4>Summary</h4><p>Team leads are laser-focused on optimizing innovation in their teams. An innovative product allows the business to create differentiation and drive success. What they do not want to do (and neither do developers), is spend time testing, or even worse, developing test cases.</p><p>However, if that testing ran in the background per commit, smoke, regression or release test — at no cost, that is an upside and would make developers be motivated to create a better product at the same time.</p><p><em>Originally published at </em><a href="https://www.testcraft.io/codeless-testing-drive-squad-velocity/"><em>www.testcraft.io</em></a><em> on July 9, 2018, by Amir Rozenberg.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d01043facf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/testcraft/how-does-codeless-testing-drive-squad-velocity-2d01043facf7">How Does Codeless Testing Drive Squad Velocity?</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>