Apologies if this is in the wrong place, I wasn't sure where else it would fit more sensibly.
I have been put in charge of QA and Test for all output from a team of DBAs and Database Developers. Help. I am from an engineering background, and despite designing databases over 10 years ago, I'm lost. What can I expect from them? I suppose that techniques similar to those used in development QA apply, such as peer review and static analysis?
Or, do I take the view, where possible, that their stuff is always validated at a higher level (when the developers submit stuff to me for test) and that the development team are responsible for debugging and going back to the data team, where their stuff is the problem? (I don't like this, though!)
Any thoughts or suggestions would be gratefully received. Thank you.
"Even when the experts all agree, they may well be mistaken."
I am not sure I understand what your thought process is except feelings of panic.
Have you talked with the DBAs and Database Developers to discuss the expectations of the end product...the database? In testing anything, best place to start is understanding the expected outcome or what is required for the system to be acceptable.
I would focus on what results your team is looking to achieve, data validity, performance of how the database populates data, stress performance, what systems access the data and how that performance is measured.
I'm sure others can add more ideas but again, carefully examine what the expectations are and from where/whom those expectations come. Then it's a matter of taking the time to analyze how to go about proving if those expectations actually exist for the database and it's behavior.
Going out of your comfort zone requires failure. True genius is measured by your recovery.