Linkin Park, “In the End”
I found this interesting article on the St. Louis Post-Dispatch Web site:
There are a lot of test articles floating through the Internet in production systems. Why people don’t bother to turn them off after the testing is done, I don’t know.
Bonus points to you if you can spot the issue with the test article itself.
If you want to be a successful consultant, you might learn something:
What defects will you log? Whatever defects you like. What is the best methodology for testing? Whatever methodology you like. What’s the best time to start automated testing? Whatever time you like.
Well, “succeed” might be a misnomer. But you’ll certainly be employable.
In This Moment, “Big Bad Wolf”
If you need more Monday morning wolfery, see also this.
This is a login screen before you can use the application, with an account name, password field, and a Log In! button.
There is bubbly copy and a licensed stock image of a bearded man holding a small boy.
> check copy
The copy is cheery, but not particularly informative. In a stunning turn of events, the words are all spelled correctly, AND they've remembered the serial comma.
> mouseover image
The title and alt text are set for the image and read "Welcome back!"
> type </html> into account name field.
The value displays in the edit box.
> type </html> into password edit box.
The value displays in the edit box.
> click Log In!
A Potentially Malicious Request warning displays! Oh, woe and agony! The site is eaten by a grue.
Well, suddenly, that’s me.
So I log a bug to indicate that the page should display a message in this case. That’s the first part of the two-fer.
Oh, and I look forward to the first through one hundredth times I have to log a bug about capitalizing CrossFit correctly.
You know I log every instance of controls/edit boxes/drop-down lists where the lower-cased g gets chopped at the bottom.
Well, except this one in the FogBugz defect tracker itself:
Internet Explorer is the worst offender in this regard, but the screenshot above is from Firefox.
Now you know why Roger Dougherty, single, born in August and living at 1021 Brighton Way, Harrisburg, Oregon always signs up for applications I test.
“The Monster” by Eminem
I’m not friend with the monsters under my bed. I’ve frightened them all away.
You know, I like to get a look at any and all artifacts as soon as possible to see if I can spot any flaws as early as I can. This includes comps, prototypes, copy, and wireframes, where I hope to catch oversights before they get into the code.
But in addition to looking for oversights, I always wanted to review the documents qua documents, especially if your company is providing wireframes, comps, prototypes, copy, and so on to the client for review. It gives you a chance to catch mistakes, misspellings, improper branding, and inconsistencies before your client can look at them and think, “Ew, these guys can’t spell our name right on the wireframes. What would they do to our Web site?”
Yes, I did review RFP responses and proposals as well.
The Purple One links to this article entitled Wireframes – Should They Really Be Tested? And If So, How?
New trainees came on board and we had a training class to learn software testing concepts. After seeing those enthusiastic faces with their almost blank-slate minds (professionally), I decided to take a detour to my routine training.
After a brief introduction, instead of talking about software testing like I normally do, I threw a question at the fresh minds – ‘Can anyone explain me what a wireframe is? ’
The answer was a pause and thus, we decided to discuss it. And that is how it started – Wireframe/Prototype Testing
This should provide a good argument and overview if you need one.
You owe it to yourself to make your new co-workers read this: Living in the Age of Software Fuckery: Ten Anti-patterns and Malpractices in Modern Software Development
Well, all except the new managers. They teach this stuff in MBA and MIS programs already. But as a good idea.
Link via iDisposable.
Last week’s Barron’s had an article that pretty much covers the best way to enjoy a long career in QA.
QA or the Highway is coming up this week, so now it’s time for our long distance dedication to the introverts at the conference. It’s Alessia Cara with “Here”:
To be honest, I’ve held entire jobs where I felt this way.
Because I just loaded it onto a cheap MP3 player for my gym workouts, have Poison, “Come Hell or High Water”:
When you log into Slack, it provides you an inspirational message. How positive of the program. This particular item always gets me:
The first item on the list is that I couldn’t complete the list in under 24 hours.
Then we get into the physically impossible.
What, this is a rhetorical question? Then why ask it?
The tale has all the hallmarks of technical debt in a huge, unmaintained, bitrotten codebase (the bug itself due to code that hadn’t been used for 8 years), and a really poor, undisciplined devops story.
I’d always sworn I’d never work for a health devices or financial services company because the risks were so great.
Well, so far, I’m keeping half of that pledge.
Fitbit owners from several US states claim that despite the company’s products purporting to accurately measure heart rates, Fitbits “do not and cannot consistently and accurately record wearers’ heart rates during the intense physical activity for which Fitbit expressly markets them”.
One claimant in the class-action lawsuit says that while her personal trainer measured her heart rate at 160 beats per minute, her Fitbit Charge HR recorded a rate of 82 bpm. Another who said his doctor had told him not to exceed 160 bpm found that his Fitbit Surge device was as much as 25 bpm below what other trackers said.
It looks as though the device derives the Beats Per Minute from a different measurement. So although it might be correct in a high percentage of cases, given enough absolute cases, it can have a high number of failures.
It’s like the new saying goes, “Where there’s an algorithm, there’s an error.”
Twitter is all a-tweet about this news:
Internet Explorer has long been the bane of many Web developers’ existence, but here’s some news to brighten your day: Internet Explorer 8, 9 and 10 are reaching ‘end of life’ on Tuesday, meaning they’re no longer supported by Microsoft.
Just because Microsoft stops supporting these things does not mean you can stop designing, developing, and testing for these old versions of IE on Wednesday.
When you’re thinking about browser compatibility, you have to judge based on actual market share and your user base’s browser statistics, not press releases.
Otherwise, you risk alienating a certain segment of your user base (“But just the uncool ones!” the kids will say) or frustrating your help desk who now has to handle the callers/emailers complaining about the site not working in IE 8.
(Actually, I am repeating myself.)
I got the 1984 Lee Aaron album Metal Queen after the holidays. One listen, and I was transported back to that era amid some inexpensive smoke effects.
To celebrate, here are three Lee Aaron tracks, although only two come from Metal Queen.
“Barely Hanging On”:
“Head Above Water”:
And, of course, “Metal Queen”: