What are the considerations for QA when (testing/) analysing the database architecture at its design stage? Relationships, normalization...what else, and how?
Anyone, please provide me with some link with details on this topic.
Thanks in advance.
Three things come to mind:
1) Are there test databases for every production database? Exactly which databases are you testing what on?
2) From the database documents, people, and other resources, gather what you'll need to run SQL SELECT statements to verify data integrity, validate that back end fields and data correlate to front end; fields that changed / didn't change, etc.; including what to run SQL statements on (are database field names same as front end field names, etc.)
3) Usually not much else in my experience. Where I've been, either non-DBAs not allowed to do much in the databases, or, its a struggle to obtain the database documents and you may not even get them. Unless ofcourse your task is specifically to test the database!
For the first 2 items above, be sure to make friends with the DBAs as well as developers that develop/control databases in the development environment!