We are implementing a testing framework, covering areas like mentioned in this SE article. But in addition, as part of unit testing (probably), we want to perform data contract testing.

The database is in SQL Server and the schema is managed through Visual Studio git code repository.

My question is are there best practices for data contract management that cover:

  • where the data contract meta-data is stored
  • how is the data contract meta-data accessed

In order to execute our data contract tests automatically, the management of the meta-data needs to be in an electronic form that is programmatically accessible - e.g. a SQL table. Also, we want to be able to include the information into word documents or PDFs becoming part of the system documentation.

1 Answer 1


Not I am not aware of any best practices.
One choice is to rely on an ORM. The updates can be async so you'll want to avoid checking it anyway.

  • Thanks for your answer Michael, could you elucidate around ORM (I'm assuming Object-relational mapping) please? Not familiar (and it will assist others who come later). thanks
    – Marcus D
    Commented Apr 10, 2017 at 15:37
  • This issue we have is a number of teams working on separate databases (OLTP / DWH) and wanting to have an agreed data structure that is easily tested against change.
    – Marcus D
    Commented Apr 10, 2017 at 15:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.