dennis

 

ReviewIn the previous two posts, we discussed some ways to look at code and pick out the test cases. These included finding the boundary test cases, input and output classes and special value testing. This time we’re going to take a departure and discuss specific practices which will help you creatively find more test cases. more »

 

Last time, in Identifying Test Cases #1, we looked at some simple examples of identifying test cases for SQL statements. This time, we’re going to look at a more complex example in the form of a database view. Our ExampleSuppose we want to know which of our employees are under the age of 18. In more »

 

It takes a lot of practice to write test cases for SQL code, and much of that practice happens on the job. One of the most important aspects in writing test cases is simply identifying what test cases to write. Normally I start by writing my first test case before I touch the code at more »

 

We’ve seen FakeTable in tSQLt in action in a few demos now. Did you know that you can use FakeTable to fake a view? You use FakeTable on a table when you want to test a procedure (or function or view) that relies on a table. It prevents you from needing to concern yourself with more »

 

It wasn’t until recently that I ever thought to do away entirely with database constraints. Aside from appropriate normalization and writing fast SQL code, much of the time database professionals spend is on figuring out exactly what constraints to put on their schema. We’re taught by textbooks and by some bad experiences that database constraints more »

© 2012 sqlity.net Suffusion theme by Sayontan Sinha