Solomon Rutzky (11/13/2008)

---

Ok, sorry, I misunderstood the intent of that question. To test both the modifications made in the Stored Procedure and the result set returned, you would do the following all within the same page:

a) use the "Query" operation calling EXEC on the Stored Procedure to test the result set
b) use the "Query" operation again calling SELECT * FROM Table1 to test that change
c) use the "Query" operation again calling SELECT * FROM Table2 to test that change

Most of the Fit fixtures you can run from Fitnesse can also be run by FitRunner.exe from the command line. You can run a DoFixture, ActionFixture, ColumnFixture, RowFixture, etc. via FitRunner.exe. Is it possible to use FitRunner.exe to execute DbFit fixtures?

Is there any way to increase the command timeout in DBFit?

Solomon, in my experience the "SELECT * FROM Table1 to test that change" approach is very inefficient. Come to think of it, next month or next year you will have to add some more test data for some other requirement, and that will break your "test that change" piece. It is much better to test exactly the change - the difference between the original and the modified states.

gojko adzic (11/21/2008)

---

for large tables, if the table has an autoincremented id, you can do something like:

|query|select max(id) as top from table|
|top|
|>>currentmax|

// do your test here

|query|select * from table where id>@currentmax|
|col1|col2|col3|

ian.gregson (2/10/2011)

---

I would like to be able to create a test around the metadata returned from a stored procedure.

My scenario :- I will receive Column A, Column B & Column C from a stored procedure.

If another developer changes the sproc to return another column, Column D, I want my test to fail.

eharper (11/21/2008)

---

Is there any way to increase the command timeout in DBFit?

I would like to test some complex data warehouse ETL stored procedures, but I've hit a problem as several run for longer than the default timeout (30 seconds), even on test data.