Have you ever seen something on a website and thought âwow!â A friendâs website has a similar domain name to another business (he registered his domain name first) and they both offer SEO services. The other business must have recently added or updated a contact form. They obviously didnât test it because as of a few days ago it routes the inquiries to my friendâs info email address. They are sending potential customers to their competitor!
Itâs amazing to me to see these types of errors. That one test, and the fact it wasnât done, has a measurable impact on their bottom line.
Well, I was made redundant from my last role because Management declared in-house development and testing to be an âunaffordable luxuryâ. Then the company moved to a new office and announced to a waiting world via social media âClick here for a virtual tour of our fantastic new city centre office!â.
When Iâve been triaging bugs, Iâve defined a high-impact bug as either an important bug that has an adverse impact on functionality or an unimportant bug that nonetheless has a high impact on the application in terms of reputation, such as a highly visible or embarrassing typo.
Again, In my last role (youâll guess that the company had Issues ) we commissioned an in-house online training tool from a third-party supplier, but no-one took responsibility for acceptance testing. When it was delivered, apart from the fact that parts of it didnât work properly, there was an introductory video which had an appalling typo (âsailersâ instead of âsailorsâ) in large type in a graphic over the CEOâs introductory voice-over. That would have gotten me instantly sacked from a previous job if Iâd had any sort of responsibility for the toolâŚ
Thatâs a good point - just because itâs a bug that doesnât impact functionality (ex/ will crash the site) doesnât mean itâs always unimportant to test. In my last role I would often get verbiage for text updates, such as new or updated questions, that were riddled with typos. I didnât mind but found it interesting that even though everyone in the office had spellcheck, it fell to me to actually use it.
At one of my past employers, the graphic design folks did not have to run any of their stuff past testing, so I never saw âthe pretty stuffâ before it went up. Would you believe: a typo in the name of the business on the LOGO?
) we commissioned an in-house online training tool from a third-party supplier, but no-one took responsibility for acceptance testing. When it was delivered, apart from the fact that parts of it didnât work properly, there was an introductory video which had an appalling typo (âsailersâ instead of âsailorsâ) in large type in a graphic over the CEOâs introductory voice-over. That would have gotten me instantly sacked from a previous job if Iâd had any sort of responsibility for the toolâŚ