Creating Specs for a data-Driven Website

Hi:

I have am creating a Website which will have numerous calls to the database when the user makes a request on the webpage.

How would it be best to document these in a spec?

At the moment I have screenshots and the database schema.

But I am not sure how it will be best to list the exceptions and database calls that need to be made.

Hamlet
Tuesday, December 23, 2003

Whoever tests it will need to know what the right result should be (for both good and bad inputs). Write the spec so a tester can be sure everything does what it's supposed to.

The tester shouldn't really care how an error is trapped/handled, only that the code handles it somehow; details of what actually happens should be in the comments.

Tom Hathaway
Tuesday, December 23, 2003

Thanks for your input.

Would there be an example online I can reference to?

Hamlet
Tuesday, December 23, 2003

http://philip.greenspun.com/panda/databases-interfacing

Is a decent article

Mike
Tuesday, December 23, 2003

The Greenspun article is like soooo out of date.

And wrapped in dot-com holier-than-thou hysteria :(

Hollandaise Sauce
Tuesday, December 23, 2003

It is old, but a lot of the guidelines still make a ton of sense.  Things like non-forking web servers and persistant database connections etc.  At the time he was writing AOL server and TCL had it all over Apache and CGI.  And yes, Philip can be a bit full of himself at times.  That doesn't make it a bad article.

Mike
Wednesday, December 24, 2003

  Recent Topics

  Fog Creek Home