www.ittopinterviewquestions.com

www.ittopinterviewquestions.com
Found some good material on software testing and CMMI

On Sun, 29 May 2005 symbianstuff@yahoo.com wrote:

> www.ittopinterviewquestions.com
> Found some good material on software testing and CMMI

Buyer beware. I looked at some of the interview questions for testing. The
answers are vague or wrong. I've interview people who prepared using stuff
like this. I'd ask them something, they'd give the answer from the web
site, I'd ask them to elaborate, they'd say something completely wrong or
just look at me without a clue what to say.

Examples of wrong answers can be found in the first few pages. For
example, Ad Hoc Testing. First, adhoc is a single word (attention to
detail is important). Second, adhoc testing is not monkey testing. Adhoc
testing is conducted by someone using experience to guide random testing.
Monkey testing is just trying random tests without any basis in
experience. For example, hold the SHIFT-ALT-CTRL keys, press Scroll lock
twice, let go and click some static text on the current dialog. This is a
monkey test. Nothing in all my experience leads me to believe this will
find a defect.

Holding the CTRL key while I right click on a part of the screen that
normally displays a context menu would be adhoc testing. Sometimes it
gives a different or unexpected result. Once I saw it give me access to an
undocumented feature the programmer used to debug the application. Too
easy to find.

Another bad example: Beta testing. You can beta test the first release of
a product. It does not need to be a re-release. I can hire people to beta
test my product. I could pick potential customers and have them beta
testing version 0.9 of my product.

I skipped ahead and found the definition of monkey testing (since adhoc
testing referred to monkey testing). Monkey testing is not "just few tests
here and there to ensure the system or an application does not crash out."
This would be more suitably called smoke testing.

I found it a good start but you really want to question all the answer.
Take the questions and search for your own answer rather than rely on the
answers given.

--
Send e-mail to: darrell dot grainger at utoronto dot ca