What is the DevOps Talks Conference? The DevOps Talks Conference (@DevOpsTalks, #dotc19) brings together DevOps leaders, engineers, and architects who are implementing DevOps principles and practices in startups and leading enterprise companies from around the globe. The conference boasts speakers from companies such as: Google, Microsoft, JFrog and more! This year the event is being held at the Melbourne Convention and Exhibition Centre (MCEC) March 21-22! Read more…
What is UKSTAR? UKSTAR (@UKSTARconf, #UKSTARConf) is a leading software testing event in London that unites software testing and quality assurance professionals from all corners of the globe. Organized by EuroSTAR, the premier testing conference in Europe, UKSTAR Conf 2019 includes two days of innovative keynotes and breakout sessions covering tracks like Automation, Modern Tester, and Leadership. Read more…
Have you tried using the new Selenium IDE for your QA test automation?
People seem to like it…
HOLLY MOLLY ! This plugin is more than AWESOME . tried a simple test and ran super smoothly. Thanks guys amazing job. Must have for automation in 2019 https://t.co/Na8fqnQ7KP
— David Bernal (@DavidBBernal) February 26, 2019
Still skeptical? I get it.
And rightfully so.
Traditionally, record and playback tools suffer from a litany of issues, including:
What is QA Financial Forum? QA Financial Forum (@QA_financial, #QAFF) has become established as the leading conference for software quality assurance and IT risk management professionals. This is an exclusive event that brings together some of the top minds in financial technology to share their digital journeys, best practices, challenges and more. The speaker line-up features companies like Bank of America, Barclays, and JP Morgan Asset Management. This year’s conference will be held at the Hilton Canary Wharf in London on February 27. Read more…
In this webinar, you’ll learn how the newly re-factored Selenium IDE is guaranteed to augment your testing efforts, regardless of your team’s automation “maturity” level, or your personal technical knowledge or experience.
Watch this session with Dave Haeffner and Tomer Steinfeld – full-time maintainers of Selenium IDE — and learn: Read more…
We’re excited to share that Applitools has once again been named to the CB Insights 2019 AI 100!
This list represents the 100 most promising privately-held artificial intelligence (AI) companies in the world. These are companies using AI to solve big challenges, and we’re honored to be recognized alongside so many well-respected and innovative companies.
How did we make the list?
Watch this in-depth session by Gil Tayar about how Test Engineers and QA pros can successfully collaborate with developers.
This webinar includes an extensive overview on test methodologies and types – especially for frontend testing – tips, tricks, and best practices on how to effectively test developer code, and how to decipher developer lingo.
The full webinar recording and Gil’s slide-deck are below.
“I will give a recipe that you can follow to ease your fear of the unknown: writing tests for developer code. At the end of this session, I guarantee that you will gain a deeper understanding of different kinds of tests, know how to decipher developer terminology, and learn how to write unit, integration, browser, and E2E tests.” — Gil Tayar. Sr. Architect & Evangelist
There is always a lot of uncertainty around which programming language to use when starting a new test automation project. Should you go with the same language that the development team is using? Or should you choose a language that has an abundance of community support so that you can easily get help when stuck? These are critical points to consider.
What our data is saying
More than half of the top ten companies in software, financial services, and healthcare verticals have enhanced their UI test automation suites with Applitools’ visual validation. With millions of tests running in our cloud every week, we’ve observed interesting trends on how these top companies are succeeding with their test automation initiatives. We’ll share these insights in a series of blog posts, starting with this one.Read more…
Tomer Steinfeld has been working as a Frontend Developer with Applitools for over a year now. He’s an expert developer and the nicest of people! His currrent focus has been rewriting Selenium IDE from scratch to bring it up to date with modern web standards. It is now both a Google Chrome extension and Firefox add-on, is written in React and MobX and does very challenging things. These include recording user interactions, playing them back, supporting many types of UI selectors, supporting interaction with other extensions to extend functionality, emitting code and exporting it, dealing with security constraints, and much more.
We sat down with Tomer to find out what brought him to work in web development and Applitools, and how he continues to learn and build on his skills within his role.
To better understand the Applitools Storybook SDK for Angular, here is a tutorial on how to build a small AngularJS application from scratch, adding some Storybook stories, and then finally performing visual regression testing using the Applitools SDK to generate snapshots for us to view and analyze.
You can find the source code for this article on GitHub by following this link storybook-angular-applitools repo.
Watch this webinar with Kent C. Dodds about frontend testing, and prepare to re-think everything you think you know about shipping apps with confidence. We want to make sure that when we ship new code, our users can use the application. The best way we’ve found to do that is to write automated tests that run before we deploy a new version of the app.
But there’s a catch with frontend testing: if our tests aren’t doing exactly what the user will do, then how do we really know that things will work when users interact with our apps?
Expert Kent C. Dodds makes us rethink everything we know about frontend testing: what it means to ship applications with confidence, and what it takes to get there. With improved tools and practices, we can be more certain that what we’re shipping to our users will work the way it’s intended. Watch his full session right here: Read more…
Take a guess: how long have we been dealing with software bugs?
It’s not 30 years, around the time Windows was first released.
It’s not 48 years, the start of the Unix epoch.
It’s actually much longer. 71 years and 2 days, to be exact. Here’s why.
Back on September 9, 1947, Grace Hopper, a Harvard computer scientist, was running tests on a calculator and found calculation errors. She did some investigation and found a moth that had landed between two solenoid contacts, shorting out an electromechanical relay. Apparently, the bug had been attracted by the warmth of the machine.
We now commemorate this occasion every September 9, Tester’s Day.
As you can see in her logbook entry below, dated September 9, the actual offending month was taped to the page. So not only is the first known example of a software bug, it’s probably the most tangible example of one as well.
“I’m now at a point in my career where my skill set is sought after by many tech companies. That is amazing to me; I have leveled up.”
For Angie Jones, leveling up is an everyday occurrence. Not only does she make sure she is consistently up-to-date in the forever changing dynamics of the tech world, but with her non-traditional job, she is afforded the opportunity to help others become better engineers as well. Angie had no idea that enrolling in her first computer programming class at Tennessee State University would lead to a career in aiding aspiring engineers around the world.
No frontend project can survive without an effective testing strategy. Why?
Because frontend projects can be as complex as backend projects — but users still expect a flawless experience. And if those users complain to your management… it’s just bad.
So, more and more frontend developers are realizing that they need to bake automated testing into their development process.
But questions remain:
We want to help you out of this.
Please join us at State of Frontend Testing, a free online event where frontend testing experts share how to quickly build high-quality web and mobile apps in 2019. We’ll cover the testing strategies, tools and frameworks you should be using in 2019.
The future of software testing is autonomy: creating programs that autonomously test applications. So should you fear for your future, or be excited by the opportunities?
Watch this special end-of-year session with Gil Tayar, and learn if AI in software testing is something to look forward to: will it make software testers better? Or obsolete? Read more…
I’m pleased to announce that Applitools has released Root Cause Analysis, or RCA for short. This new offering allows you to instantly pinpoint the root cause of visual bugs in your front-end code. I’d like to explain why RCA matters to you, and how it’ll help you in your work.
Well, maybe RCA doesn’t find THE root cause. After all, all software bugs are created by people, as the Dilbert cartoon above points out.
But when you’re fixing visual bugs in your web apps, you need a bit more information than what Dilbert is presenting above.
What we’ve seen in our experience is that, when you find a bug in your front-end UI, you need to answer the question: what has changed?
I regularly use Jenkins CI and GitHub to help our customers integrate Applitools into their continuous integration workflow. Even though I’m pretty familiar with both tools, there’s one thing that drives me nuts.
Here’s the problem:
I can’t see Jenkins build status in my GitHub repo pull request. Below is a screenshot of a typical GitHub pull request. As you can see, there’s no indication of my Jenkins build status.
This forces me to leave GitHub and go to Jenkins every time I merge, just so I can check the build status.
Doing this once is no big deal. But after doing this for a hundred pull requests, I feel like pulling my hair out. (And that would just look weird.)
On September 9, 1947, Grace Hopper recorded the first computer bug ever in the Harvard Mark II computer’s logbook. The bug in question? Believe it or not, an actual bug – a moth – flew into the relay contacts in the computer and got stuck. Hopper duly taped the moth into the logbook. Then she added the explanation: “First actual case of bug being found.” (This might be the most famous moth in history.)
If only things were this simple today. As software continuously grows in complexity, so does the process of testing and debugging. Nowadays, the lifecycle of a bug in software can be lengthy, costly, and frustrating.Read more…