I just started testing the product and one thing that is an annoyance for me is that when you run a test, the blue for selected row drowns out the check mark. This makes it hard to see when the task is actually finished. Perhas excluding that cell from being highlighted row would be the easiest fix.

Context menu option on all nodes in the SQL Test panel - with the following options:
a. on the db node - "Script all tests" (scripts every test, and all classes)
b. on a test class node - "Script all tests" (scripts all tests that belong to that class, and the class)
c. on an individual test - "Script test"

More looking for an answer to this problem (trying to automate the install of SQL Tests on a newly created database using Team City.

If it doesn't exist then can it be added?

TST is another open source framework for Unit testing sql server stored procedures. It would be great if the test runner supported this framework as well.

I docked my TEST window in the bottom right left hand corner, under my Object Explorer. But each time I reopen SSMS, it is floating again. One time it was almost completely off the screen to the left. Can you please have it stay docked?

tSQLt allows you to have class-specific set up SPs (called setup in the class schema). However I can't find an option to create these directly within SSMS. Perhaps a right click on the class to allow you to edit / create a setup script, as well as some way of visualising that a setup script exists for a given class within the SQL Test window.

When you refresh the tree all nodes are expanded. This is very frustrating when you have many test schemas and tests. Ideally a refresh should do the following:
1) Not change whether a node is expanded or collapsed
2) Apply to the node at which the refresh was done. If I select refresh from the context menu for a class then it should only refresh that node

EXEC tSQLt.RunAll; -- ctrl-0 doesnt refresh the visual UI

I would assume this to be non-trivial, but in learning about testing with application code, I find code coverage tools invaluable.

When your tests fail you should be able to close the window using escape key

It appears that there may be something wrong with the test ordering in SQL Test. I have about 50 tests in my current db project split into about 5 TestClasses. For some reason the tests under one of the schema's are not ordered alphabetically. I have check the tSQLt tests view and my tests order correctly in the view. Any ideas why this might be happening

It would be helpful to have a test count per test class and total test count. It would also be nice to have a count of tests passed and tests failed.

This test failed for objects which had decimals defined as decimal ( 3, 5) Note the spaces.

Currently it is not possible to remove a test class (and all tests associated with the test class) via the SQL Test interface. This would be another nice to have / productivity feature

It would be really helpful to be able to rename a test or the testclass from the test context menu

When I restore a database - either from backup or source control - tests are not shown automatically in the SQLTest window. By adding the database to SQLTest it shows the authored test, but it would be helpful if this process was automatic. This would be particularly helpful in multi-developer projects where tests are not necessarily written by the same person.

The @@identity test also takes the phrase @@identity into account when it exists in comments. I have some procedures that already have this changed, but a changelog comment inside the code also raises this error.

I want to test a proc that adds a record to a table. If I create an empty fakeTable and add a record to it I would expect it to have a value in the "ID" filed according to the IDENTITY(x,y) constraint of the field. It appears FakeTable drops that constraing. Is there a way to add it. I'm not sure the "name" of that constraint in order to use it in a call to tSQLt.Applyconstraint.