November 9, 2012
Dear Everyone:
In the evenings, I typically watch some old TV show until about 10:00
(Pacific Time). Then, just
before switching the TV off, I tune it to a channel that will have local
news on when I wake up in the morning.
I did this last Tuesday and was just in time to catch the tail-end of
Twit’s Condescension Speech.
“…I tried so very hard (to save the world)…but the Nation (idiots that
they are!) chose the
President instead…I will pray for him.”
Well! That’s a relief!
Here I was wondering what would happen if the “better man” won
and it turns out, it doesn’t matter.
Twit will personally intercede with The Almighty on the
President’s behalf. How
magnanimous!
All I can say is, Thank God (or Whoever) that we won’t have to spend the
next four years listening to that patronizing tone of voice.
In other election news…
Sales taxes are going up here in California, but nearly all the other
Propositions went down in flames.
Here’s to “Just Say No!”
Meanwhile, at work…
We are, once again, busily
testing.
This time it’s for a Fourth Quarter RFC (Request For Change) that
will be released in December.
Basically, all the “defects” that were renamed “enhancements”
will be expected to show up in Production next month.
But first, we have to test them all.
The software that we have been using to manage “defects” also allows you
to manage the tests. In
fact, it has this nifty little feature called a “module”.
Here’s an example that you can try at home:
(Premise: You are going to
log into your email.)
Step One: If you are already
logged into your email system, log out.
(Did that work? If yes, you
Pass!!!)
Step Two: Navigate to the
email login screen.
(Did that work? If yes, you
Pass!!!)
Step Three: Type in your
Login ID and password.
(Did the system allow you to type in to the provided fields?
If yes, you Pass!!!)
Step Four: Click the Login
button.
(Did you actually get into the system?
If yes, you Pass!!!)
Now, because many, many tests begin with logging into the system, only
changing which Test User ID you’re using, you can put these four simple
steps into a Module called “Login”.
In every Test that starts with logging in, instead of typing in
(or copy-paste) these four steps (which are really only three steps if
you’re paying attention), you can simply “call” the “Login Module”.
Another Module walks the User through testing that certain fields are
“Required” in certain forms.
By adding just these two Modules to a Test, you’ve added many, many
(however unnecessary) steps very quickly and easily.
We call this “padding”. It
makes it look like you’ve been slaving away over a hot keyboard all day.
However, there is a drawback.
(There’s always a drawback.)
If something goes wrong in a Module, it goes wrong in every Test
that you’ve plugged that Module into.
For instance, remember that one where you tested that a certain field
was Required? What happens
when the Developers decide that it’s not so Required after all?
In a word, Kablooey!!! Your
Test just failed!!! (Bad,
bad, Test!)
When this happens, “Ludmilla”, who is positively bonded to her beloved
Modules, squalls like an angry two-year-old and flings the “F” word (and
other assorted four-letter words
not-appropriate-to-use-in-an-office-environment) around with abandon.
(Bad, bad, Test!)
So I’ve been spending my days “testing the Tests” to find all the places
where the original Modules are based on outdated, or incorrect, data.
Thus exposing many, many “Bad, bad, Tests!”
There’s a lot of them. The
Result: Ludmilla is Not a
Happy Camper right now.
But the weekend is upon us.
“Jeannie” wants to go to a Free Kitten Faire.
And we don’t have to listen to that annoying patronizing tone of
voice anymore.
Love, as always,
Pete
| Previous | Next |