• Subject: Re: Software testing scripts
  • From: Richard Baird <rbbaird@xxxxxxxxxxx>
  • Date: Thu, 04 Dec 1997 21:56:56 -0500
  • Organization: Premium Systems, Inc.

> All --
> My current client manufactures pharmaceuticals, and therefore software testing
> is very important. To this end, they prepare a "test script" for each program;
> a step-by-step checklist.
> Theoretically, this is an _exhaustive_ test; as exhaustive as reasonably
> possible. In reality, a lot gets missed.

Been there, done that.  Just got back from an 8 month contract at a
prominent Indianapolis based pharmaceuticals corporation who shall
remain nameless ......."Eli's Comin'"......  Cobol shop, cubicle jungle,
darned to heck by phil, the prince of insufficient light

I think it's an FDA requirement to have test scripts for all programs. 
and the last thing a drug company want's to do is cross the FDA.  Just
getting audited by them can set back a new drug's release a year or two,
even if they don't find anything wrong.  

> Creating the script is a real time-consuming hassle. Basically, a programmer
> (me at this point!) must go through the program, attempt everything, and 
> every action. That log, in turn, must be converted into a script. Believe you
> me, it's VERY involved.

You bet, I was amazed at the hoops you had to jump through just to make
a one line change to an installed program!!!  tested, verified,
validated, approved by two others, documented in 3 separate places,
promoted, signed off by 4 others-in triplicate, logged.....  GIVE ME A

The hardest thing to get used to was my lack of authorization to do
anything.  I've always had fairly significant security clearance at most
every client I've worked for, but there, the analysts have the LOWEST
security clearance.  You couldn't even run an update program in a
production environment.  After a while, it started to actually perfect
sense, because the data was so sensitive, only the users could and
should be responsible for it.

> Today, while musing about this, I was able to develop a "model" for the "Work

<big snip>

> I'm excited about this program, and hopefully I'll find the time this weekend
> to write it.

you got time? what's a weekend?  :(
> Is this something that appeals to anyone else? Does anyone else write test
> scripts?

They might, but how easy could it be modified to accept several
"templates" of different types of programs?  they may write 2 or 3 new
"work with" programs a year, and they just modify the existing script
for changes to existing ones.
> -- Don "how about a script for test?" Schenck

If a program writes a test script of itself, how would you know if it
was correct? :)


| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].