Marc,
Yes, I agree may be its not fair to put a number on it but I know I got few questions wrong because of typos and I do think its fair to say so because I know it for a fact. When you write a test, you can tell which question you have answered correctly and which ones you arent sure about.
Here is one question that I must have gotten wrong and if I didnt then we have a bigger problem than just typos.
One dragndrop question asked me to put the correct param tag in place. The two options given were [obviously incorrect choice] and [another incorrect choice, but less obviously so]. There was no option with correct closed param tag. I chose the latter one thinking this must be the correct answer and I must have missed it in specs but if you read specs the only correct answer could be formatted like: <
jsp aram name="something" value="something"/> and it was not one of the possible answers for the question so I got this one wrong because
of a typo. Correct? Because if you say that Sun might have assumed [obviously incorrect choice] to be correct then we have a bigger problem than just typos...
Another one was the inclusion of the file with wrong file name. I was confused if I should pick "none of the above" or the correct include and assume its a typo. Yet another one had all the incorrect file names
and no "None of the above" option.
The point I am trying to make here is that a developer writing the test shouldnt be worrying about typos and errors in the test itself. These errors in test should be fixed and I am going to email
somebody @ Sun about it.
Please dont worry about the last post because I think I repeated what I said in my last post here again.
Thanks,
Mahrukh.
[I removed the details of the actual question because even the bad questions are copyrighted. - Marc]
[ June 18, 2007: Message edited by: Marc Peabody ]
[ June 18, 2007: Message edited by: Marc Peabody ]