T.S.T. the T-SQL Test Tool

Closed Issue: Overall XML Status always yields "Failed" when using RunSuite [10030]

lmolnar — Thu, 16 May 2013 07:20:26 GMT

In the Internal.PrintHeaderForSession procedure, the variable @TestSessionStatusString will always end up as Failed because of a missing ELSE:
IF (@TestSessionStatus = 1) SET @TestSessionStatusString = 'Passed'
SET @TestSessionStatusString = 'Failed'
Should be
IF (@TestSessionStatus = 1) SET @TestSessionStatusString = 'Passed' ELSE SET @TestSessionStatusString = 'Failed' End

Closed Issue: Can the server and database name be added to the generated xml? [10160]

lmolnar — Thu, 16 May 2013 07:20:26 GMT

Since we have multiple databases on multiple servers, it would be very usefull to have the database and server name included in the results xml.
Following variable and function can be used: @@servername and DB_NAME()
This way we can use xslt to create a report on the results.
<TST status="Failed" testSessionId="79" start="08:42:39" finish="08:42:40" duration="560" >
Would then become:
<TST server="server" database="database" status="Failed" testSessionId="79" start="08:42:39" finish="08:42:40" duration="560" >

Closed Issue: IsLike not working if LIKE pattern > 4000 chars [10311]

lmolnar — Thu, 16 May 2013 07:20:25 GMT

The Assert.IsLike and IsNotLike procedures don't work if the ExpectedLikeValue is bigger than 4000 characters. This is a limitation of sql server.
Adjust the procedures to use nvarchar(4000) as data type of the @ExpectedLikeValue parameter to make this clear.

Closed Issue: Add Assert.String(Not)Equals to the API [10312]

lmolnar — Thu, 16 May 2013 07:20:25 GMT

For (N)VARCHAR(max) strings, the Assert.Equals API cannot be used.
Since the IsLike procedure does not handle big patterns either, the API should be extended with a StringEquals call to allow the comparison of big strings.

New Post: Testing login permissions

JohnMayo — Thu, 02 May 2013 18:26:28 GMT

I need to write tests to validate the permissions for various application logins. I'm planning on using the EXECUTE AS LOGIN = 'ApplicationLogin'; and REVERT statements in the tests. Is that the best way to tackle this problem? Any advice on how best to test permissions?

Created Issue: Invalid object name '#Tmp_CrtSessionInfo'. [11722]

igolferd — Mon, 22 Apr 2013 03:02:31 GMT

when I run
DECLARE @BinaryString varchar(8)

SET @BinaryString = dbo.QFn_TinyintToBinary(NULL)

EXEC TST.Assert.IsNull 'Case: NULL', @BinaryString

I get back message

Msg 208, Level 16, State 0, Procedure Pass, Line 14
Invalid object name '#Tmp_CrtSessionInfo'.

Created Issue: Schema as a prefix? [11663]

mcerrato — Tue, 26 Mar 2013 21:43:44 GMT

I would like it if you could change the prefix to be a schema instead. Is that possible?

For instance, then you could implement this naming convention:

dbo.sprocToTest --for your procedure

SQLTest.sprocToTest --TST test sproc

New Post: Change TST.Bat to allow for UserName/Password instead of only supporting trusted connections

JohnMayo — Thu, 17 Jan 2013 23:22:02 GMT

In the next version, can you please change the TST.Bat file to allow a username/password combination to be used when a trusted connection can't be used.

Commented Issue: Cannot connect to remote server (linked server) through TST [11506]

SQLSCT — Thu, 17 Jan 2013 22:21:35 GMT

My TST db and test DB are in one sql server and I am trying to connect to the remote sql server though TST stored proc. And its failed with error

LE DB provider "SQLNCLI10" for linked server "SomeDB" returned message "The transaction manager has disabled its support for remote/network transactions.".

If I run the same stored proc indepenedantly form the server , it works fine. But no through TST. Does TST supports remote execution? Please reply!!
Comments: ** Comment from web user: SQLSCT **

I just want to mention that 'select statemens't to remote server works fine through TST. But wont let me to execute 'Delete statements' and this is kind of important to execute my test scenarios. But same delete works fine through a non TST stored proc. So its not a user access issue for sure.

Created Issue: Cannot connect to remote server (linked server) through TST [11506]

SQLSCT — Thu, 17 Jan 2013 21:32:54 GMT

Source code checked in, #79962

Project Collection Service Accounts — Mon, 01 Oct 2012 21:14:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #79961

Project Collection Service Accounts — Mon, 01 Oct 2012 21:08:39 GMT

Checked in by server upgrade

Updated Wiki: Home

lmolnar — Thu, 12 Jul 2012 08:48:48 GMT

Welcome to T.S.T.

TST is a tool that simplifies writing and running automated tests for code written in T-SQL. At the core of the TST tool is the TST database. This database contains a series of stored procedures that represent a test API. Part of this API is similar with that found in Unit Testing libraries familiar to programmers in C# or Java.

Feature Highlights

Support for validating views as well as stored procedures and functions that return a table.
A reliable implementation of Assert.Equals / Assert.NotEquals procedures. They detect when a comparison should not be made due to incompatibility of the data types. Additional procedures like Assert.NumericEquals, Assert.NumericNotEquals, Assert.FloatEquals, Assert.FloatNotEquals are provided.
Can run concurrent test sessions against the same or different databases.
Can generate XML results.
Automatic rollback of the database changes done during each test.
TST will detect when its own rollback mechanism becomes ineffective in some scenarios that involve testing code that uses transactions. The TST rollback can be disabled at the test, suite or global level.
No need to register the test stored procedures; they are picked up automatically by the TST test runners.
Can be run from the command prompt or directly by calling one of the test runner stored procedures.
The TST infrastructure is isolated in a separate database.
Easy to install and integrate with other test frameworks.
Does not have any dependencies besides SQL Server.
Very small learning curve for someone already familiar with T-SQL.

Current release: Version 1.9

Related project on CodePlex:
Managed Code Interface for T-SQL Test Tool http://www.codeplex.com/MCI4TST.

Complete documentation including a Quick Start section:

PDF format: TST.pdf
HTML format: TST.mht
Word 2010 file: TST.docx

7 minutes video demo: http://www.youtube.com/watch?v=bLtK20bl7G4

Author's home page and other projects: http://www.ladimolnar.com.

The TST API

Assert.LogInfo
Assert.Pass
Assert.Fail
Assert.Equals
Assert.NotEquals
Assert.NumericEquals
Assert.NumericNotEquals
Assert.FloatEquals
Assert.FloatNotEquals
Assert.NVarCharMaxEquals
Assert.NVarCharMaxNotEquals
Assert.IsLike
Assert.IsNotLike
Assert.IsNull
Assert.IsNotNull
Assert.TableEquals
Assert.IsTableEmpty
Assert.IsTableNotEmpty
Assert.RegisterExpectedError
Assert.Ignore

Runner.RunAll
Runner.RunSuite
Runner.RunTest

Utils.SetConfiguration

Updated Wiki: Home

lmolnar — Thu, 12 Jul 2012 08:48:18 GMT

Welcome to T.S.T.

TST is a tool that simplifies writing and running automated tests for code written in T-SQL. At the core of the TST tool is the TST database. This database contains a series of stored procedures that represent a test API. Part of this API is similar with those found in Unit Testing libraries familiar to programmers in C# or Java.

Feature Highlights

Support for validating views as well as stored procedures and functions that return a table.
A reliable implementation of Assert.Equals / Assert.NotEquals procedures. They detect when a comparison should not be made due to incompatibility of the data types. Additional procedures like Assert.NumericEquals, Assert.NumericNotEquals, Assert.FloatEquals, Assert.FloatNotEquals are provided.
Can run concurrent test sessions against the same or different databases.
Can generate XML results.
Automatic rollback of the database changes done during each test.
TST will detect when its own rollback mechanism becomes ineffective in some scenarios that involve testing code that uses transactions. The TST rollback can be disabled at the test, suite or global level.
No need to register the test stored procedures; they are picked up automatically by the TST test runners.
Can be run from the command prompt or directly by calling one of the test runner stored procedures.
The TST infrastructure is isolated in a separate database.
Easy to install and integrate with other test frameworks.
Does not have any dependencies besides SQL Server.
Very small learning curve for someone already familiar with T-SQL.

PDF format: TST.pdf
HTML format: TST.mht
Word 2010 file: TST.docx

7 minutes video demo: http://www.youtube.com/watch?v=bLtK20bl7G4

Author's home page and other projects: http://www.ladimolnar.com.

The TST API

Assert.LogInfo
Assert.Pass
Assert.Fail
Assert.Equals
Assert.NotEquals
Assert.NumericEquals
Assert.NumericNotEquals
Assert.FloatEquals
Assert.FloatNotEquals
Assert.NVarCharMaxEquals
Assert.NVarCharMaxNotEquals
Assert.IsLike
Assert.IsNotLike
Assert.IsNull
Assert.IsNotNull
Assert.TableEquals
Assert.IsTableEmpty
Assert.IsTableNotEmpty
Assert.RegisterExpectedError
Assert.Ignore

Runner.RunAll
Runner.RunSuite
Runner.RunTest

Utils.SetConfiguration

New Post: Output XML in JUnit format for CI?

johnmayo — Tue, 26 Jun 2012 03:56:59 GMT

If you work on the JUnit XML approach, please post here how that worked out for you.

New Post: Output XML in JUnit format for CI?

larsthorup — Tue, 26 Jun 2012 03:07:36 GMT

Thank you for your input! I can see that outputting TeamCity tags might work for TeamCity. However, I would like to have a more generic solution, and still believe that outputting in the generic JUnit XML format might be useful.

New Post: code coverage

johnmayo — Mon, 25 Jun 2012 21:49:33 GMT

No, I haven't made these extensions available yet. I need to clean up the code and put tests around the functionality and haven't had the time to do so yet.

New Post: Output XML in JUnit format for CI?

johnmayo — Mon, 25 Jun 2012 20:52:24 GMT

I was able to to integrate TST tests with TeamCity by creating a version of Internal.RunOneSuiteInternal that prints out a few things around the test:

##teamcity[testStarted name=''TestNameGoesHere"]

And after the test either:

##teamcity[testFinished name=''TestNameGoesHere'' duration=''TestDurationGoesHere']

##teamcity[testFailed name=''TestNameGoesHere'']

depending if the test passed or failed.

I put that version of Internal.RunOneSuiteInternal in a different database along with modified versions of versions of the Runner.RunAll, Runner.RunSuite, Internal.RunTestSession and Internal.RunOneSuiteInternal that called it. The change was pretty easy. I've also added statement coverage statistics to that code. Clean up the code and getting some tests around it are one of my backburner projects.

New Post: Output XML in JUnit format for CI?

larsthorup — Mon, 25 Jun 2012 04:13:22 GMT

I would like to run my T.S.T tests on TeamCity or Jenkins for Continuous Integration. I believe the XML format currently produced by T.S.T is not consumable directly by TeamCity or Jenkins. Would I have to write an XSLT transformation to the ubiquitous JUnit format myself, or is there some such transformation available already? Or are there better way to reach my goal?

New Post: How does Assert.TableEquals work?

lmolnar — Sat, 02 Jun 2012 23:59:41 GMT

Yes, #ExpectedResult and #ActualResult are the one that are compared and this cannot be changed. Take a look at the documentation where this is explained in details. The TST QUICK start database has some examples as well.