Under review

Warewolf testing Framework - Possible Process improvement - A better / faster way to generate unit tests in future

Wynand Vermaak 4 months ago in Studio / Output updated 4 months ago 3

Hi team,

We have noticed that when we debug a Main workflow, that contains several child workflow, we are able to see the full debug for the process. However, when we click the "Create a new test" button on the Debug Output, as per snip below, the test that gets generated only populates the inputs and outputs of the Main workflow - meaning the variables, objects and or recordsets associated with the child workflows doesn't populate or pull through - 

Image 1140

The current reality of how it is working currently is that we then have to manually populate all the other variables / objects and / or recordsets for the inputs / outputs of the child workflows in order to get the test to pass, else it will fail. Some of the variables like GUIDS are also unique with each execution, and because we are unable to copy and paste from the debug output we need to manually type these out. We work with some complex and large Main workflows with a lot child workflows, which means by manually filling in these variables, objects or recordsets can easily take 35 - 45 mins to complete for one test. 

Is there a better, faster, more accurate way of generating unit tests in the future?

A discussed low hanging fruit was to allow the ability to copy inputs / outputs from the debug output.

Please share your thinking of what is possible - we can put our heads together and come up with a good - viable long term solution that can enhance the dev process (Time and accuracy).



debug studio variables workflow

DateTime Tool - Incorrect InputDate given in Debug

Wynand Vermaak 2 years ago in Studio / Output updated by anonymous 2 years ago 1

Hi team,

Please refer to the screenshot below.

1. Pls look at current DateTime in the far lower right corner of the snip = 2022-04-12 12:31

2. Tool is set to add 10 minutes

3. When executed, in the debug pane, Input date should be 2022-04-12 12:31, however, it is currently giving the Output DateTime's value as the Input DateTime.

Image 1026



debug studio tool workflow

SQL Error: Error converting data type nvarchar to int

Edgar Gárate 6 years ago in Studio / Output updated by Grommit 5 years ago 4

Running the same example of the SQL video Connector in debugging mark data type conversion error, the stored procedure has an integer type parameter, in the query analyzer the stored procedure works well

Image 562

Image 563

Image 561

database debug designer variables

Debug issues

Wallis Buchan 8 years ago in Studio / Output updated by Gandalf 7 years ago 2

I am having issues with debug (both in debug output and in browser). Everything is set up up accurately as per Warewolf user guides.

I am running the latest release v1.2.1.7 on a Win10 machine.

Any suggestions?

Image 318

debug studio

Problem with Debug - downloading file instead of showing in browser

Anonymous 8 years ago in Studio / Output updated by Gandalf 8 years ago 3

Hi team

The latest release ( has a bug when running a micro service, instead of showing up in the browser it downloads a xml or json file, it was working fine on the previous version. I did some debugging, it happens only when a recordset containing data from a store procedure is configured as output (see the attached image). if I click Debug, and then select "View in Browser(F7)", instead of showing it, a xml file is downloaded (see link)
Robin Perdomo Image 305

Gandalf 8 years ago

Hi Robin

Thanks for coming through to the community. The part of the process you are talking about is handled by your browser. Please check your browser settings:

# If you return a small result set (a few lines of xml) does it still do this?

# If you use a different browser as default does it still do this?

Some browsers (like IE) will not show JSON results as text and will force a save. Others (like Chrome) will only accept a small amount of response data without forcing you to save it.

Not a bug

Not passing through parameters when calling a proc

Alex Hampel 11 years ago in Studio / Output updated by Gandalf 11 years ago 2

the input parameter I enter when debugging is not being passed through to the proc meaning a null value is being passed to the proc when calling it.

Even if I enter a default parameter value for the proc this still is not being passed to the proc?

Gandalf 11 years ago

If your Service is not returning any information, make sure you have got the right inputs and outputs specified, by clicking the  icon in the top right of the service.