Database validation - Guidance on how a database should be validated?

[cochranemurray]

Is there any guidance on how a database should be validated?

[asutherland]

Input a number into the data base, then quere the data base as to what number you just put in.

[VitaliKravitzki]

I'd suggest you to get a "DB Sniffer" software - the one that allws to track any changes in DB, and it's better be API/CLI operated one. Once you got it, build harness test script that will do the following:

1. initate activity (what final user may do...)
2. sniff db
3. compare the change to expectation (you should build those expectations by spec)



Vitali Kravitzki

http://www.interece.com

[Miner]

Originally Posted by cochranemurray

Is there any guidance on how a database should be validated?

Consider performing an FMEA looking at potential failure modes from several perspectives such as:

User inputs information correctly, but database introduces errors.
User inputs information incorrectly (e.g., typos, extra spaces, etc.)

Validation could then consist of testing the potential failure modes, and ruling them out.

[JWenmeekers]

I take first the list of requirements, to see if all the requirements are there.

The requirements list will give you all the points to check, from imput to output, the how and why and what and when etc.

If they aren't, it's a first hold point.

HTH