Archive for July, 2019

QA Music: Setting the Mood for the Week

Monday, July 29th, 2019 by The Director

You might not want to turn this one up if you work in a workplace that requires a tie. Or pants.

Dope, “Die, Motherf—er, Die”

Or maybe you do.

Conference Call Background Sounds That Require Some Explanation

Friday, July 26th, 2019 by The Director

As you probably don’t know, ungentle reader, your humble narrator has taken it upon himself to participate in triathlons at his advanced age because something in him seeks out hobbies that are even less pleasant than his daytime job.

So I have recently acquired a Volodyne 5000 Volumetric Exerciser to try to improve my lung capacity.

My thinking is that I can increase my lung capacity which will make me a better athlete and able to focus not so much on how my breathing hurts when I’m swimming, biking, or running, and that I can, instead, focus on the important things, such as how much I hate swimming, biking, or running.

So it sits on my desk, and every so often, I take a couple minutes to use it. If you’re not familiar with such a device, basically it measures how much you can inhale at any given time, so to use it, you inhale as much as you can and hold your breath for a couple of seconds.

Which sounds kind of like something else.

So I am afraid I’ll use it when my microphone is not muted on a conference call and where video is not enabled.

Ah, well, as I always say, it’s best not to explain to the other callers what is going on. Let their imaginations go. Cat fight on the desk? Continue talking as though nothing is happening. Maybe they’ll think it’s someone else on the call.

A Memorial to Rutger Hauer: Reposting the Rutger Hauer School of Software Testing

Thursday, July 25th, 2019 by The Director

Ruger Hauer passed away; in memory of him, I’m reposting something from 2012.


The Rutger Hauer School of Software Testing

As I mentioned on Twitter, I’m a member of the Rutger Hauer school of software testing. The Rutger Hauer school of software testing (RHSoST) focuses less on processes and procedures and more on how to wreak havoc using a varied set of tools upon a system or application regardless of its plot, I mean, its business rules.

But here are some of the primary texts of the school:

  • Introduction:
    Beyond Justice. The basic primer in software testing describes how to create user scenarios to test systems, how to understand and work within and without established processes and procedures, and how to turn erstwhile enemies into allies.
     
  • Exploratory Testing, Basic:
    Blind Fury. Even when you lack basic knowledge about a system or insight into the business rules or considerations, you can still cause damage find defects with your sword basic set of test cases that apply to any application.
     
  • Exploratory Testing, Advanced:
    Blade Runner. As your knowledge of applications grows, you can find more complexity and higher levels of business rules to test until the final deadline.
     
  • Load Testing:
    Escape from Sobibor. Learn how careful planning and execution of load tests can find the weaknesses in and actually crash the most rigid set of rules and constraints in an application.
     
  • Career Planning: Working in a Large Corporation:
    Deadlock. Learn how to find a payoff even when constrained by an explosive device bolted to your neck, figuratively speaking (and literally).
     
  • Career Planning: Working as a Test Consultant:
    Hobo with a Shotgun. This text deals with the itinerant tester and the challenges he/she faces with each new engagement, including how one fits in–or does not fit in–with the existing culture and how one can test effectively and efficiently on the run.
     

Rutger Hauer on the end of a project and the knowledge lost when a test consultant or team member moves on:

These are some of my favorite texts in the RHSoST. Undoubtedly, some of my fellow school members have their own. Don’t be afraid to share in the comments.

Debugging Automated Tests, Step One

Wednesday, July 24th, 2019 by The Director

Step on in troubleshooting any failing automated test should always be Look at the application and try to do what the automated test does.

I hate to admit how many times I’ve spent hours trying to debug an automated test only to realize at the end that the automated test was failing because the application had an error.

I guess I spent that much time on it because somehow I trust my own code less than code created by a software developer.

At any rate, Trish Khoo has written an automated test debugging cheat sheet that does not include my step one as step one, but it’s a handy bit of thinking to keep at hand.

Perhaps I’ve Read Too Much Theology

Tuesday, July 23rd, 2019 by The Director

Perhaps I’ve read too much theology (I was this close to trying for a triple English/Philosophy/Theology major at the university and have continued to read in the field after school), but when I saw this job posting:

I thought it was an Principal Technical Eschaton Engineer.

Which I feel eminently qualified for. I have a lot of experience telling important people that it’s the end of the world.

QA Music: Monsters

Monday, July 22nd, 2019 by The Director

It’s been a while since we’ve had any Shinedown on the blog, so here’s “Monsters”:

I know, it’s been a while since we’ve had anything on the blog. I’m working on it.

Computer Error In Company’s Favor

Thursday, July 18th, 2019 by The Director

Uber glitch overcharges customers 100 times their fares:

An apparent Uber glitch resulted in some customers of the ridesharing company being charged 100 times their advertised fares on Wednesday.

One customer wrote on Twitter that she was charged $1,308 for her Uber ride — sparking a fraud alert from her credit card company — instead of the advertised fare of $13.08. Others reported similar overcharging, including one person who expected an $8.79 fee for her ride but instead was charged $879.

The cynic in me says that bugs that cost the company money get hotfixed faster than the ones that lend the company extra money.

When Testers Go Bad

Wednesday, July 17th, 2019 by The Director

Former Microsoft Software Engineer Charged with Mail Fraud for Scheme to Steal Digital Value Such as Gift Cards:

A former Microsoft software engineer was arrested today and charged in a criminal complaint charging him with mail fraud for a scheme to steal $10 million in digital currency from Microsoft, announced U.S. Attorney Brian T. Moran. VOLODYMYR KVASHUK, 25, a Ukrainian citizen residing in Renton, Washington, worked first as a contractor at Microsoft and then as an employee from August 2016 until he was fired in June 2018. KVASHUK was involved in the testing of Microsoft’s online retail sales platform, and used that testing access to steal “currency stored value” such as gift cards. The complaint alleges KVASHUK resold the value on the internet, using the proceeds to purchase a $160,000 Tesla vehicle and a $1.6 million dollar lakefront home. KVASHUK made his initial appearance in U.S. District Court in Seattle today and is detained pending a further hearing on Friday July 19, 2019.

I’m just kidding about the testers going bad; testers start out bad, but mostly we’re bad to do good.


wordpress visitors