tsql - Unit testing a SQL code generator -

The team I am currently writing to generate a TSQL code that will be saved as a script and Will be played later. We are finding it difficult to separate our unit test during testing of code generator parts and to test the actual code we have created.

I have read, but I hope some special examples can be in the types of unit testing cases.

For example, suppose I have a little code which, according to the View schema and name, generates a DROP statement for only one view. Do I just test that the derived code matches some expected results using string comparison and later on integration or system testing ensures that the drop actually leaves the scene, if it does not, then some Also, if there is no visual or error, if the scene is one that we are not allowing one drop?

Thanks for any advice!

It is advisable to test this code that you want to generate first. When you know that this code works, you can proxy the stars mentioned.