TST Issue Tracker Rss Feed

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.

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

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

Commented Issue: Add sp procedure to the master for running the Unit Tests [10161]

lmolnar — Sun, 01 Apr 2012 03:02:46 GMT

We have created an sp procedure (sp_utf_run - which is according to our naming convention) that is deployed on the master database. This allows us to run the unit tests more easily.
We assign a SSMS keyboard shortcut to this procedure (e.g. Ctrl-9).
When we are in a query window and
- have no text selected, pressing Ctrl-9 will launch RunAll for the current database
- have a unit test selected (starting with the correct prefix), pressing Ctrl-9 will launch RunTest for the specific test
- have a suite name selected, pressing Ctrl-9 will launch RunSuite for the specific suite

This means we no longer have to type TST.Runner.RunXYZ ... to run the unit test.
Maybe this feature can be included in the project. Code added.
Defaults for verbose and format can be changed in the procedure template. We opted for verbose on and format Text.
Maybe the proc needs to be changed if schema's are used. We always deploy under dbo.
Comments: ** Comment from web user: lmolnar **

Nice idea but I will have to postpone this until a next version..

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

lmolnar — Sun, 01 Apr 2012 02:59:49 GMT

Fixed in V1.9.

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

lmolnar — Sun, 01 Apr 2012 02:59:21 GMT

Fixed in V1.9.

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

lmolnar — Sun, 01 Apr 2012 02:58:50 GMT

Implemented in V1.9.

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

lmolnar — Sun, 01 Apr 2012 02:58:14 GMT

Fixed in V1.9.

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

lmolnar — Sun, 25 Mar 2012 03:27:22 GMT

The APIs will be called: Assert.NVarCharMaxEquals, Assert.NVarCharMaxNotEquals.

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

lmolnar — Sun, 25 Mar 2012 03:26:11 GMT

ETA: April 7th or earlier.

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

lmolnar — Sun, 25 Mar 2012 03:24:49 GMT

ETA: April 7th or earlier.

Closed Feature: Make prefix 'SQLTest_' configurable [9662]

lmolnar — Fri, 23 Mar 2012 11:40:16 GMT

Currently the stored procedures require to have the prefix 'SQLTest_'.
Since we only use lower case object names and use prefixes like t_ for tables, p_ for procedures, f_ for functions, etc. it would be more logical to use ut_ as prefix for our unit tests.
It would be nice if this setting could be stored somewhere and used.

I implemented this myself. I used the TSTParameters table to store the setting.
I added a new parameter 'UnitTestPrefix', but only allowed this to be defined at TestSession level and for scope 'All'.
I did add an option to use a global setting, by using TestSessionId = 0. This to prevent to having to define a TSTConfig procedure for all our databases.

I changed all procs that now use the literal 'SQLTest_', either by passing the prefix to it or by determining the prefix inside the proc via the function below.

Changed SQL objects:
- New Function: SFN_UnitTestPrefix
- Altered Utils.SetConfiguration to be able to set the setting via TSTConfig
- Calculated @UnitTestPrefix inside 'Internal.PrepareTestSessionInformation'
- Added @UnitTestPrefix as input parameter to: 'Internal.SuiteExists' and 'Internal.AnalyzeSprocName'

Full code provided in attached file.

cfr also Topic http://tst.codeplex.com/discussions/276160
Comments:

Was fixed in V 1.8

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

lmolnar — Fri, 23 Mar 2012 11:38:26 GMT

Correction: ETA: April 7th or earlier.

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

lmolnar — Fri, 23 Mar 2012 11:37:21 GMT

Correction: ETA: April 7th or earlier.

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

lmolnar — Fri, 23 Mar 2012 06:19:47 GMT

ETA: March 7th or earlier.