Comments on: Automating T-SQL Testing

By: jayant das

jayant das — Fri, 22 Jan 2010 08:22:22 +0000

This is great article for sql server developer

Regards
Jayant Das
9313406257

By: Yury

Yury — Thu, 27 Aug 2009 17:35:43 +0000

OK. Sending it to your GMail address…

Thanks a LOT!

By: Jeremiah Peschka

Jeremiah Peschka — Thu, 27 Aug 2009 17:19:18 +0000

Yury, do you think you could paste your full SQL either in the comments or send it to me in an email? Being able to see the whole picture would help out a lot.

My info is available at: http://facility9.com/about/getting-in-touch/

By: Yury

Yury — Thu, 27 Aug 2009 16:48:50 +0000

Jeramiah,

Thank you very much for looking into this and for fixing that! I really appreciate it, there was no confusing: I am glad I found this code!

The code runs fine now. However, I am now seeing something else results-wise…

The sproc takes in login name and spits out a true/false depending whether the login is valid.

What I am getting now is the error table with an entry for each run with the same error message:
“Procedure or function ‘prc_CheckLogin’ expects parameter ‘@LoginName’, which was not supplied”

More specifics…

The #temp table shows:
ProcName Run ParamOrder x
prc_CheckLogin 1 1 @LoginName = ”
prc_CheckLogin 2 1 @LoginName = ‘nonexistent’

The #procs table shows:
Command
EXEC prc_CheckLogin @LoginName = ”
EXEC prc_CheckLogin @LoginName = ‘nonexistent’

Somehow, it doesn’t execute the command correctly. In the code, I substituted –myprc– with OtherDB.dbo.prc_checklogin since that sp sits in the different db but on the same server, and it doesn’t look like it can’t access the proc since commands are executed just fine…

Any suggestions?

As always, appreciate your time,

-Yury

By: Jeremiah Peschka

Jeremiah Peschka — Thu, 27 Aug 2009 14:49:56 +0000

Yury, I fixed the issue. It basically boils down to using [TEXT()] instead of [text()] in the query. The T-SQL syntax highlighter that I am using was capitalizing the TEXT because it is also a data type. Let me know if you keep having problems with this code and I’ll help out however I can. Sorry about any confusing that mistake may have caused.

By: Yury

Yury — Wed, 26 Aug 2009 21:40:10 +0000

Hi Jeremiah,

I came across this method of testing the sproc and I really like it. I am a QA Engineer and we are thinking of adopting that script for our testing purposes.

I am not an expert in SQL but I could easily follow the steps. So, so far, I created a table and populated it with some seed data for the sproc I am trying to test.

Then I modified the last chank of code as follows:
1. Replaced test.[Procedures] with proper DB (actually just left Procedures)
2. Replaced –myproc– with exec MyDB.dbo.MyProc

When I ran it, I got whole bunch of errors:
#1. Complain about invalid XML identifier in Text() as required by FOR XML; ‘(‘ is the first character at fault
#2. When I removed () around this column name, I got: “Incorrect syntax near the keyword ‘EXEC’. Msg 156, Level 15, State 1. Line 34 AND also Incorrect syntax near ‘>’, same line.

Any suggestions to make this script run? Appreciate it.
-Yury