SQL Test Suggestions

I have been really getting more involved with SQL Test and tSQLt since HamishWatson presentation at PASS this year. As part of that I have been compiling a list of features or enhancements to the SQL Test application to make it more intuitive and speed up productivity with the tool. I have been funneling these suggestions through my Redgate Account Executive since there isn't a UserVoice for SQL Test. I wanted to pass them along to the FoRG group to get their input and if they have any suggestions based on their usage of the product.

Here's the list I have compiled so far:

1. Allow users to copy/move a test from one Test Class to a different Test Class
a.) If an existing test exists, notify the user that an existing test exists and create the new test with “_Copy (##)” at the end to indicate that it is the newly moved test
b.) Alternatively, prompt the user to provide a new name for the test so that it won’t overwrite the existing test that has the same name

2. Allow for a “smart rename” functionality to rename any internal references to the source test so that when the test is moved that the references in test references the destination Test Class that was specified

3. Allow users to filter the databases that are listed in the left pane. The reason for this is If I have a lot of databases that have tSQLt installed on them, but only really deal with a couple databases, I would like to be able to hide the ones that are not used as frequently. Maybe something like in SQL Prompt how you can specify “Connections” for Suggestions and either “load all databases”, “only load certain databases” or “don’t load certain databases”. When you choose “only load certain databases” or “don’t load certain databases” you provide a list of databases that can either be shown or not show based on which filtering method you chose. The default is “Load all databases”. I would think this would be easy to implement since it is already something done in SQL Prompt so the code might be reusable?

4. Allow for tSQLt tests and core objects (those objects in the “tSQLt” schema) be hidden in SSMS and only visible within SQL Test. This would clean up the SSMS tree for developers and reduce the amount of scrolling. I know that SSMS has the ability to setup “Filters” on the nodes so I could setup filters but that would be very repetitive to have to set that up for each database that we have tSQLt test. This would be something that would allow for one place to filter out those specific objects and only show them in the SQL Test.

5. When the user right clicks on a Test Class and clicks “Run Tests” it should cause the test class node to refresh so that the user can see any tests added since the last time the GUI was refreshed so that the user can see the results of the test. It would be more intuitive than requiring the user to right click the Test Class, then refresh, then right click again to run the tests.

6. The “Delete Test” and “New Test” functions already refresh the test class node so this would just make this consistent with other operations

adam_hafner February 13, 2019 15:20