Red Herring Top 100 recognized the most promising privately-held companies in North America, and Applitools was recognized for its Application Visual Management market expansion leveraging AI Powered Visual UI Testing.
It’s always an honor to be recognized for your hard work. So when the 2018 Red Herring Top 100 North America Awards were announced, and Applitools was included, we were both excited and humbled to be included on this prestigious list alongside some amazing and innovative growth companies.
In the days before web applications, programmers wrote applications for a specific platform and used that platform’s native development environment and user interface controls. Before the application’s final release, a tester would check that the application was ready. Some testers wrote elaborate documents that described complicated scenarios they performed on the software manually. Other, more adventurous testers used fancy tools that were the quality assurance version of Microsoft’s Word and Excel macro recorders. A tester would record a series of actions on the software under test. These steps were recorded in a high-level language in which the tester could edit the code and add test conditions that would verify that the actual results of the test matched the expected results. Each time a test was run, a report was generated that showed which conditions had been passed or failed.
Award program recognizes the leaders in the software development space, and this year, Applitools brings visual UI testing to the community.
Recently, SD Times, the leading monthly magazine for Software and Development Managers, DevOps teams, Test & QA professionals and CIO’s announced their annual SD Times 100 awards, and Applitools was named a “Best in Show” for the software testing category.
It’s not often that software testing makes the news, but when it does, it’s usually because something within the test automation has gone spectacularly wrong. At 8:05 AM on January 13, 2018, the Hawaii Emergency Management Agency sent out a false missile alert. While there is much that is still unclear regarding exactly what happened, most reports agree that an internal test was treated as a real event. According to The Washington Post, part of the problem may have been caused by a human operator who chose the “Missile alert” instead of the “Test missile alert” from an application menu.
At some point while each of us were growing up, we wished that the adults in our lives would just disappear. They made our lives miserable with their arbitrary rules and restrictions, but they got to do all kinds of fun things. After all, how hard could it be to drive a car, and why did we need them to watch an R-rated movie or to cross the street?
Well, front end developers have a similar fantasy. Their wish is that one day, all back end developers will move out of their way and let them take control. Front end developers are responsible for the things people see and use. All the back end developers need to do is create REST APIs and HTTP endpoints that work and return well-formed JSON, and the front end developers do the rest.
We have some exciting news to share as we end the week. In recognition of our innovative visual UI testing and monitoring technology, we’ve been selected as a finalist for the Red Herring 100 North America. Every year Red Herring recognizes the most promising privately-held companies in North America based upon their technological innovation, management strength, market size, investor record, customer acquisition, and financial health. During the months leading up to today’s announcement, Red Herring reviewed over 1,200 companies in the telecommunications, security, cloud, software, hardware, biotech, mobile and other industries that completed their submissions to qualify for the award.
Have you ever asked yourself why all apps aren’t web apps? Well, this is actually already the case on desktops and most of the apps you use at home and/or at work. When it comes to productivity apps, Microsoft, Apple, and Google all have full-featured web apps that are just as capable as locally installed desktop applications. As long as you have good wired or wireless internet, you can do nearly all of your work in Chrome, Edge, or Safari. Apart from specific categories, such as graphics, video editing, software development, and high-end gaming, you can do nearly everything in a web browser.
Mobile, however, is a different story.
It is probably safe to assume that any developers reading this article are already testing their applications. At the bare minimum, you’re testing the feature you’re working on as you develop it and checking that it works with any existing code. Many of you are probably using some form of automated functional testing as well. These types of testing are certainly important and they help to ensure that your applications work as expected, but adding visual testing into the mix will improve your testing significantly.
Today, users access applications in a variety of ways, including wearables, smartphones, tablets, laptops, desktop PCs and an increasing range of smart devices. Now, developers need to account for the ways in which these new and diverse technologies change how their software is presented to and perceived by their users. The typical forms of testing we’ve relied upon for so long simply can’t detect the problems that may exist on every possible device. This is why developers now need to test the visual aspects of their applications. In recent years, developers have started using visual testing methods, tools, and frameworks to meet these new challenges.
In this post, we make the case that it’s wise to use visual testing. Even if you, your team, or your organization are old hands at automated functional testing, we’ll explain why you should add visual testing into your existing infrastructure. We also offer advice about available tools, frameworks and solutions that will help you get started. Whether you’re a novice developer or a seasoned veteran, the information presented in this post will help you deliver the best experience for your users.
At an industry event recently I had the opportunity to listen to a keynote by Janet Gregory, co-author of “Agile Testing” and “More Agile Testing”. During the talk, Janet asked the audience to pair up. One person stood facing the stage and projected slides, the other to face away. The person facing the slides was to tell their partner what they saw. They had 5 minutes to describe in every detail what was going on in the picture. The person facing away was told to visualize it. To try to remember and visualize every detail spoken to them.
When the clock ticked down and the five minutes were up. Janet asked the folks facing away from the image if they thought they had a good visualization of the image. Of course they did, they’d just heard 5 minutes worth of words detailing it.
Then she asked everyone to look at the image.
Whether you’re a test automation engineer or a manual tester, it’s crucial to track what your test environment is. This enables your developers to easily replicate bugs found and avoids the frustration of not being able to reproduce those problems.
It’s also important to track your web or mobile app user interface history using a UI version control system. This helps your developers, product managers, and designers understand what’s been tried, what’s worked, and what hasn’t worked so that the entire team can iterate the UI rapidly, in an Agile fashion, to a product that works well for customers.
The Better Software West conference (#BetterSoftwareCon) is here and we couldn’t be more excited! Catch us in Vegas from June 6-7, as Gold Sponsors of the event regarded as the show for promoting and educating attendees on – you guessed it – building better software. It is co-located with Agile Dev West and DevOps West, offering three conference programs to choose from.
Watch this webinar, presented by Sr. Software Engineer Justin Ison, to find out about the crucial information automated exploratory tests give us on our native mobile app, and learn Justin’s proven step-by-step “How-to and Best Practices” Guide to automated exploratory testing.