|Earliest: November 26, 2017||Latest: May 20, 2019||Total: 61|
|May 20, 2019|
Finding QA "misses" that has happened in Massachusetts has been tricky. Every company has their issues, and not all of it makes the headlines.
I did manage to find these two stories when QA Testing would have helped avoid the public embarrassment. I'll continue to look and when I find others, I'll link them to this post:
The Dorchester Historical Society sent out postcards in mid-November letting people know of an upcoming open house. The problem was that the wording of the card. The card read: " We're dreaming of a white Dorchester."
Once people got the postcard, they started complaining on social media on the double meaning of the message. The Dorchester Historical Society realized the mistake and responded on social media that they were removing the graphic from social media.
We are very truly sorry about our graphic used for this event. This was an unfortunate oversight on our part and the event photograph has been removed from our social media. We were simply changing the words to the classic Christmas carol and did not think it through properly. https://t.co/2Anki4JF6N— Dorchester Historical Society (@DotHistorical) November 26, 2018
Lesson We All Can Learn From This
It doesn't hurt to test the Holiday Card design in front of customers or employees. Find out what they think of it. It's not only a chance to see if the intended message gets across but if there's anything that needs to be corrected.
In April 2018, the Massachusetts RMV send notices to more than 9,000 drivers that their licenses would be suspended because of outstanding fines.
The notices were wrong as the recently installed software had a technical glitch. The RMV identified the problem immediately and send out additional letters to drivers letting them know of the mistake. In addition, they put notices on their website and in the wait queue when calling the DMV.
Lesson We All Can Learn From This
Always Test, Test, Test, new software implementations. It cost the DMV a lot of money to fix the issue - mailing additional letters and updating various customer point of contacts.
You didn't need to test to make sure that all the addresses are qualified matches - but a good sample would have indicated a problem with the DB query.
|May 13, 2019|
Software Testing is very important to every organization. You don't want customers to have a bad experience and you don't want your organization to look bad.
Here are a couple of examples of where a bug slipped QA and made it into production:
Turns out that the Reserve Bank of Australia (RBA) spelled "responsibility" as "responsibilty" on millions of the new yellow notes.
The RBA has confirmed that there was at least one typo on the note and will be fixed in the next printing. For now, 46-million banknotes will have the small misprinting.
FYI: The A$50 is one of the most popular notes that is circulated in Australia.
For more details
For a brief few hours on New Year's Day Cathay Pacific Airways sold thousands of first and business-class seats for huge discounts.
Seats that normally would go for $16,000 were selling for $675.
Cathay has publicly announced that it would honor all such seat prices.
Happy 2019 all, and to those who bought our good - VERY good surprise ?special? on New Year?s Day, yes - we made a mistake but we look forward to welcoming you on board with your ticket issued. Hope this will make your 2019 ?special? too!— Cathay Pacific (@cathaypacific) January 2, 2019
Next week I'll highlight some costly QA mistakes in Massachusetts.
|May 6, 2019|
If you're doing any type of QA Automation, you'll likely run into XPATH. You'll need that to identify components on a webpage for interaction. You may want to click a button or simply verify that functionality is working.
You can learn a lot more about XPaths in Selenium over on Guru99.
All the modern browsers have a cool way to get the XPATH of an object:
It turns out that FireFox is the only browser that returns the Absolute Path of an XPath. All the other browsers return the Relative XPath value.
Here's the difference of when I selected the same element on a page using different browsers:
Uses the Absolute XPath when you copy the XPath.
|March 25, 2019|
If you haven't heard, Adobe Flash is going away. Adobe has announced that it will no longer supported by December 31, 2020.
Starting in July, Chrome will start warning users that Flash will no longer be supported after December 2020. You should only see this anytime you load up a website that still has Flash.
This will start appearing in Chrome desktop version 76 ? which is expected to ship in July.
Check out the Chrome Browser Release Schedule.
Many people consider the demise of Adobe Flash started when Steve Job wouldn't allow it to run on any iOS devices.
July 10, 2015 - Third Zero Day for Flash. Various Technology sites report another major security hole was encountered in Flash. There is no available fix from Adobe. This is the second major Flash bug found in a five-day period.
July 12, 2015 - Firefox started blocking all Flash Content from running automaticlly. Users are able to run flash by clicking on the "Allowed" button.
September, 2015 - Google started blocking non-essential content. Content that is smaller than 300x400 pixels - Websites that ran fully on Flash were not impacted.
September 1, 2016 - Google started blocking Flash-based page analytics and background processes.
December 15, 2016 - Google Started Blocking Flash-based videos and content. Users had to enable Flash once visiting a website for the first time.
January 1, 2017 - Microsoft Edge started Blocking Flash Content.
Check out the relevant links on the bottom of the page for more interesting links.
The US Government has decided to remove Adobe Flash from their websites by the end of July 2019. Senator Ron Wyden has asked government agencies to remove the usage of Flash-based plugins from the websites of the Federal government.
|March 18, 2019|
What this means is that typical formatting won’t work anymore. That’s really bad if you used keyboard shortcuts to paste in code or snippets. The good news is that Markdown is being used by more and more applications - such as Slack and Notion. So learning Markdown isn’t a bad thing.
Blocks of code are either fenced by lines with three back-ticks ``` or are indented with four spaces.
..some text ```
One of the things I link about the new editor is that I can paste in the Markdown from another editor and the formatting gets applied on Paste. Using the menu options seems to be good for some quick typing.
If your new to Markdown, check out the guide over on ghost.org. There are plenty of other documentations available - the best way to learn is to use a note taking app such as Notion or Bear.
One of the features that I liked in the old system was the graphical emoticons, especially the Green Checkmark and the white X in the red box. These were perfect for bullet points so people can instantly see what issues are not working.
These are history in the newest Markdown adaption. You'll now have to use the Emoji equivalence:
|?||U+2620||Danger, Will Robertson|
|March 11, 2019|
Sometime QA testing involves detail testing - making sure that images and page positioning are to spec.
For this the best tool is Page Ruler Redux. It's not a tool that I used frequently, but it does help in those instances when the page elements just don't look right. It's really handy in screenshots - people can clearly see if there's an issue.
Draw a ruler to get pixel dimensions and positioning, and measure elements on any web page.
You can get the Page Ruler Redux Extensions in the Chrome Store.
Page Ruler Redux is only available for Chrome, they are working on a Firefox version.
|March 4, 2019|
|February 25, 2019|
Blue Button Chrome extension, by the Voice Group, is a handy way to get some quick information about the site you are currently looking at.
Hit the Blue Button on any web page, and get an instant, no-frills index of its building blocks. Easily access information on SEO, code and graphics components: from title tags and meta description to scripts and stylesheets to images and fonts.
Did you know that the image alt tag is required anytime an image is referenced? Blue Button makes sure all the images have the proper Alt tag. QA should note images that don't have the proper Alt tags - which will help SEO.
|February 18, 2019|
This is a free report - you do have to fill in some contact information to get the report. I suspect that this is used to contact you to help gather data for next year's report.
The World Quality Report, which this year interviewed over 1700 respondents from 32 countries, is the only global report analyzing application quality and testing trends. It has been produced annually since 2009.
Now in its 10th edition, the 2018-19 report adopted data collection through computer-aided telephone interviews. Based on analysis of six respondent groups: CIO, VP Application, IT Director, QA/Testing Manager, CDO/CMO, and CTO/Product Head, the report surveyed respondents from across the globe through quantitative interviews followed by qualitative deep-dive discussions.
I am not going to go through all the data in the report. The report encompasses 72 pages, and there's lots of useful information for any type of QA Testing.
I would highly recommend getting the report and reading all the information. It's a good way to understand the trends around the world.
|February 11, 2019|
More and more organizations are using Slack as their main communication tool. Knowing some tips/tricks can help QA deliver messages to the team more efficiently.
Here's three style tips on using Slack:
Replying to issues and comments via Slack thread can help de-clutter release day noise. To start a thread, simply hover over the message and click on 'Start a thread' icon.
More tips on Threads on the Slack help page.
By using thread to manage issues, new issues won't get distracted by all the conversations of a previously reported issue.
Add the appropriate icon before your message so people can instantly know what's going on:
Using backticks on branch names helps make the branch stand out. That way people can quickly identify the branch when they are scanning the Slack conversations.
I have a Keyboard Maestro action set up so that it automatically post the build status of a Git build in a particular Slack channel. This way I don't have to worry about informing the team of the action.