by Michael S. Kaplan, published on 2012/05/02 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2012/05/02/10299780.aspx
Our story thus far:
It was almost 4½ years ago that I wrote some basic rules.
Rules for developers.
Rules for developers about keyboards.
I was even faux pompous enough to refer to them as my Michael's Keyboard Laws for Developers. :-)
The first law: VK_A is not always 'A'.
The second law: Not every keyboard contains every VK_* value.
The third law: Not every keyboard contains every character.
The fourth law: Not every individual keystroke is relevant.
The fifth law: <CTRL>+<C> and <CTRL>+<ALT>+C will stop each other from doing their jobs, and <CTRL>+<ALT>+C is the same thing as <ALTGR>+<C>
Now after that last law, law #5, a question comes up.
After the rules and regulations about development and how it impacts and is impacted by keyboards is laid out in Michael's Five Commandments, I mean.
It is a question near and dear to the heart of most SDE/Ts and STEs....
Who owns keyboard testing?
Now that is a complicated question!
The short answser is simple!
The detailed answer is that it depends on the kind of testing you are referring to.
The breakdown is simple:
it is possible that if you are one of those types of testers that you may feel that this breakdown is unfair - particularly if it relates to an unanticipated test resource requirements.
Unfortunately, no other breakout makes much sense, and other schemes will lead to incomplete coverage, and (by the First Software Tester's Axiom) will lead to bugs.
Unless what you really want is to have bugs.
Maybe I should send some email to your manager? :-)
go to newer or older post, or back to index or month or day