You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using dbfit from fitSharp distribution. I've noticed that I cannot use the Inspect fixture in standalone mode, because there is no way to set its "mode" (e.g. QUERY, TABLE, or PROCEDURE) in standalone. I'd like to be able to do this.
So...
Can the Inspect fixture be changed so that perhaps it can be extended to allow "mode" to be set ("mode" is currently private), say with an InspectQuery class, InspectTable class, and InspectProcedure class; each of which can just set the "mode" to the appropriate value.
This would have the added benefit of allowing usage of "Inspect Query" to work in fitnesse regardless of being in flow mode or not (without having to change the fixture name in the test from "Inspect Query" to "Inspect" or vice versa).
The text was updated successfully, but these errors were encountered:
I'm using dbfit from fitSharp distribution. I've noticed that I cannot use the Inspect fixture in standalone mode, because there is no way to set its "mode" (e.g. QUERY, TABLE, or PROCEDURE) in standalone. I'd like to be able to do this.
So...
Can the Inspect fixture be changed so that perhaps it can be extended to allow "mode" to be set ("mode" is currently private), say with an InspectQuery class, InspectTable class, and InspectProcedure class; each of which can just set the "mode" to the appropriate value.
This would have the added benefit of allowing usage of "Inspect Query" to work in fitnesse regardless of being in flow mode or not (without having to change the fixture name in the test from "Inspect Query" to "Inspect" or vice versa).
The text was updated successfully, but these errors were encountered: