| || |
User Tom Ba (firstname.lastname@example.org) posted:
Yes, testers do all of the above and more.
Sometimes do too much.
Manual test good, sometimes no need to automate,
especially if one-off application.
Writing down is good, using Word is good,
sometimes it all doesn’t matter.
Example timely tip from ‘42:
When testing the berryllium trigger,
be CERTAIN to separate it from the
plutonium implosion core
by at LEAST 3 feet.
Figured this one out
20 yrs after radiation dimmed
----Original Message Follows----
From: Aidy Rutter <AidyR@TrustMarque.com>
Reply-To: "SQA Suite Team Test Users" <email@example.com>
To: "SQA Suite Team Test Users" <firstname.lastname@example.org>
Subject: Manual & Automation
Date: Tue, 5 Jun 2001 10:52:42 +0100
Do testers out there automate directly from use-cases/low-level
requirements, or do they run a manual test first and then automate?
Do they write down the test steps of the manual test? Do they keep this in
word or Rational ManualTest?
Do you think it's a good idea to write down the test steps first, then