Insights Blog Software Testing vs. Football


Software Testing vs. Football

With the big game coming up, our tester minds run wild...

This Sunday is the Big Game, and for those of you testers (the Bug Game!) out there who think you know the terminology, I’d like to educate you.  The first definition is what software testers would use, and the second definition is for fans of American football.

Attempt: Test run. A kick, carry or throw.

Backward pass: Regression test.  A negative-yardage throw.

Blocker: A bug that prevents other testing.  Defenseman.

Bomb: Fail spectacularly.  A long arcing pass.

Box: Content holder on a page, or a checkbox/tickbox for short.   A strong safe section behind the ball.

Center: Request to position text or graphics on a midpoint.  An offensive position who often snaps the ball.

Clipping: Graphical bug of text and/or image being cut off.  An unfair block that results in a 15-yard penalty.

Coach: Manager or mentor that will help a tester to grow.  The guy everybody blames when the team loses a game.

Conversion: Data migration.  Extra point(s) connected to a field goal.

Counter: A value holder that increments upon usage.  A running play with a directional fakeout.

Down: System state when you want to use it.  Unit of game play.

Drive: Storage location.  Plays pushing for extra yardage.

Encroachment: Getting too near a manager.  Illegally crossing the line of scrimmage and attacking before the initial snap.

Extra point: Any valid ROI key benefit.  A single point scored in a conversion attempt by making what would be  field goal in regular play.

Fair catch: A bug that Development will accept.  Catching the opponent’s kick.

Forward progress: What you tell yourself when the project seems to be failing.  Yardage gain during a down.

Fullback:  The number of bugs that were not the developer’s fault.  A player whose primary job is to make room for the person actually carrying the ball.

Fumble:  When nobody knows that the deliverable is past due.  When the player drops the ball onto the field of play.

Game manager: Whoever organizes afterwork fun.  Type of successful quarterback.

Halfback:  The number of bugs that are still in the system after patching.  A player standing near the Quarterback who runs the ball.

Handoff: In silo methodologies, moving the build to a different department.  Passing the ball without the ball being in the air untouched.

Holder: Data storage locale.  Place kick assistant.

Hurry-up offense: Rudely telling your manager that you’re testing as fast as you can and that if you’re allowed to get off Skype and the phone, you’ll finish it already!  Maximizing yardage while minimizing clock time.

Illegal formation: Corrupted data.  On offense, not having seven on the line of scrimmage for at least one count before the snap.

Illegal shift: Overflowing the high bit.  Offensive pre-snap motion constraints.

Incomplete pass: The test case was successful but you messed up the paperwork.  The throw wasn’t caught.

Jammer: A fuzzer for web app testing.  Someone who slows down gunners during the punt.

Kicker:  The hidden parts of projects that make them more difficult or less intelligent.  Player who kicks the ball.

Kneel: Prayer seems like the best course of action.  A low-risk way to run the clock after catching the snap.

NFL: Answer to “Will testing be done on time after you got the final build a month late?” which includes “Not” and “Likely”.  National Football League.

Package: A release build.  A group of players on the field for a given play.

Pass: Make it through a test case OK.  Throw the ball.

Pick: Select from a dropdown.  A pass interception.

QB: Last letters in ISTQB (an SQA certificate).  Quarterback.

Quarterback:  The number of bugs after patching that the developers knew about but said were fixed anyway.  Player in command of the offense.

Red shirt: Nameless Star Trek security officer who won’t survive the episode.  A college player who sits out a season so they can make it up later.

Sack:  What you hit after a long day of testing.  Tackling the QB behind the line while he still has the ball.

Safety: Testing concern, specifically security testing.  A way to score 2 points.

Spike: Extreme increase in resource usage.  A play where the QB throws straight at the turf right after a snap.

Suicide squad: Movie that would have been better if the Joker got more screen time.  The kickoff and punting teams.


Let us know if you can think of any others.