Test Planning for A Level?

[RobDoh]

Hi

I'm currently doing an ICT A Level project involving an Access database. For part of the specification I have to do a "Testing Plan". I've done the testing strategy, which just describes what elements of the database I will test. The testing plan is supposed to contain a grid including every single test that will carried out, the expected outcome etc.

Basically, I need a good guide to do this. I've looked in my Access 2002 "Bible" and no luck there and I've searched the web and had no luck also. Maybe I'm searching for the wrong thing.

Any help would be greatly appreciated.

Thanks.
Robin.

 

[k209310]

Hell

try WHITE and BLACK box testing. They are pretty standard testing methods I think. White tests the staructure black tests the functionalitly of the software.
Not too sure if this is what you need or not

Hope it helps tho

Chris

 

[Fornatian]

Surely if you have written the testing strategy, then the testing plan should be a natural progression from there. Depending on complexity of the database, you should consider building tests for the following:

• Basic Design - Does it satisfy normalisation according to your ERD.
• Table Structure
• Relationships and Join Types
• Field Types and Indexing Strategies
• Object Names and Descriptions - were naming conventions followed, do you understand why you built those queries in the first place?
• Form Design - is it pleasing on the eye? Does it do what it's supposed to
• Forms, what happens if you enter erroneous data?
• Same as Forms for Reports
• (Form and Class)Module Code - are they commented so anyone can understand ?
• Oh, and don't forget to offer some recommendations on how it could have been done better, many marks are earned in humility if you can state why it's wrong, the reasons and a proposed solution.

Any more advice?

 

[RobDoh]

k209etc : that wasn't really what I was looking for but thanks anyway.

Thanks a lot Ian That's very useful...

Know what to do now

 

[Fornatian]

Just quote this anf get out of it the work completely:

PETS

People for Ethical Treatment of Software (PETS) announced today that more software companies have been added to the group's "watch list" of companies that regularly practice software testing. "There is no need for software to be mistreated in this way so that companies like these can market new products," said Ken Grandola, spokesperson for PETS. "Alternative methods of testing these products are available."

According to PETS, these companies force software to undergo lengthy and arduous tests, often without rest, for hours or days at a time. Employees are assigned to "break" the software by any means necessary, and inside sources report that they often joke about "torturing" the software.

"It's no joke," said Grandola. "Innocent programs, from the day they are compiled, are cooped up in tiny rooms and "crashed" for hours on end. They spend their whole lives on dirty, ill-maintained computers, and are unceremoniously deleted when they're not needed any more." Grandola said the software is kept in unsanitary conditions and is infested with bugs. "We know that alternatives to this horror exist," he said, citing industry giant Microsoft Corporation as a company that has become successful without resorting to software testing.