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.
For years, front-end developers have dealt with the pain of browser-based bugs and the difficulty of testing hundreds of scenarios. They’re itching for help with front-end testing, but have struggled to find a solution that scales past a few simple tests. They have the skills to write test automation, just not the support.
Now, more than ever, is the time to team up front-end developers with QA teams. So much functionality has shifted to the front-end that past practices will no longer work. We need to focus on solid solutions that have been proven in the workforce.
In this session — hosted by Kevin Lamping, Front-end Engineer and Consultant — you’ll learn how you can build a Front-end Testing Discipline using cutting-edge tools and techniques, along with patterns to follow in organizations at various levels.
Here are some of the talking points Kevin covers in this session:
Why is Jira so hard to use for bug tracking? This seems to be a continual refrain heard on the web: “Jira isn’t suited for Agile development”. “Jira is complex and bloated”. “People cram too much information into Jira”. Another common complaint is that Jira tickets are simply unmanageable.
Organizing JIRA tickets pic.twitter.com/2YeDNc7tcf
— Mike Herchel (@mikeherchel) October 2, 2017
But, love it or hate it, Atlassian Jira is very popular for bug tracking and can be found within many software development organizations worldwide. If your workplace is one of the many that uses Jira, you might want to consider using Applitools Eyes to make your visual user interface (UI) testing easier.
First, some background: Applitools Eyes lets you automate visual UI testing of your web and mobile application front end. Using Applitools Eyes ensures that your application’s UI is displayed consistently and accurately across any device, browser, or viewport. Atlassian Jira manages your development workflow, task tracking, issue management, and reporting.
Testers get a hard time sometimes: as soon as something is put in front of us, we tend to find problems with it. A skill some value, others not so much. However, we aren’t the only people blessed with this ability, hello designers!
Those problems get fixed, you test a bit more, and declare yourself done. You then sit down with the designer to review the implementation, and immediately: “Wrong! Wrong, that’s wrong”. “That’s the wrong font”. “Ahhh, that’s not the right blue”. “That margin is too small”.
I’m sure you’ve heard similar things. So why didn’t we find these issues? Of course there are infinite reasons, but I want to explore a common one: Inattentional Blindness. Read more…