I’d do some research on the tool, first off to see how easy it is to get started with the tool:
- How good is the official documentation
- Does the tool have an active community of users
- How long the tool has been around
- Ask for opinions from your team members - this can also provide you with useful insight
- Try to find people how used the tool already and talk to them
- Analyse your needs (and the needs of your project) to see if the tool meets those needs
- Does it integrate well with existing tools - if this is required
- Trial and error - you learn the most about a tool by trying it on in action. Use it to try to solve a real-time problem you are having at work
In companies I’ve worked in so far the DB testing was done by the DB Admins and/or the DevOps teams.
However, I was always curious about that kind of testing and I’ve done research in the past - just in case someone in the future asks me to preform testing on a database.
The xUnit family of testing frameworks has extensions for doing database testing - for example JUnit has the DbUnit extension which can be used for testing relations databases using Java. Microsoft (SQL Server) and Oracle (Oracle SQL Developer) also have DB testing functionality built into their tools.
For no-tabular databases, like Mongo, there is NoSQLUnit which also relies on JUnit. There are plenty of other DB testing tools to take a look at, here’s a handy article on that topic.
There were a few questions in the AMA which I wanted to get back to and add a few more details to my answers, I’ll do that once the recording is available.