Answered

Error when saving scenario in Automatic Testing Tool: "Error: Undefined action"

I'm attempting to use the Automatic Testing Tool with an extremely simple test process which contains a pair of radio buttons. The radio button selected determines the path through the process.

When I press "Stop" to end the recording Bizagi shows:

  1. The recording cannot be performed. Check the console for errors!

The message displayed in the console on the test tool is:

  1. The Recorder service is starting...
  2. Configuring Recorder Service....
  3. Recorder Service Configurated !
  4. The Recorder service is ready.
  5. Launching Recorder Interface: http://test_server:10024/AutoTest2/jquery/automatictesting/test/Recorder.html
  6. Preparing to save scenario....
  7. Error when saving scenario.Error: Undefined action
  8. Parameter name: STARTPROCESS

The log files of the recording and execution are attached.

What have I done wrong?

Comments (13)

photo
1

Additionally, I believe this originates from the http://localhost/AutoTesting.svc/Recorder/SendRecordedRequests which is returning an HTTP status code 400 (Bad Request).

I've attached the raw payload and the parsed 'requests' portion. "STARTPROCESS" is only mentioned once

photo
1

Dear Graham,

Make sure that your IIS is correctly installed according this article: http://help.bizagi.com/bpm-suite/en/index.html?prerequisites_iis.htm

After that, check these articles from our help site in order to record and run autotesting tool:

Best Regards

photo
1

fd3764d018ff0a93bfd0096d3314150a

  • ASP.Net frameworks is registered with IIS.
  • Server Operations Service has been reinstalled.
  • The Automatic Testing Tool is configured correctly, connects to the database fine (I know this because it wasn't connecting previously until I made SQL Express visible over TCP)
  • I'm running the Automatic Testing Tool as admin.

Everything works until the tool attempts to save the recorded session at which point it says:

  1. Error when saving scenario.Error: Undefined action
  2. Parameter name: STARTPROCESS

photo
1

Dear Graham,

In order to identify what is going on, we require the following information:

  • Bizagi Studio version (Right click on exe file and see on properties > details tab)
  • Automatic Testing Tool version (Right click on exe file and see on properties > details tab)

We look forward to hearing from you

photo
1

BizAgiStudio.exe :: 11.0.0.2574

Bizagi.AutoTest.UI.exe :: 10.7.0.2083

Automatic Testing Tool was downloaded via: http://www.bizagi.com/docs/Autotesting.zip I've just re-downloaded it to check that there isn't a v11 (in case the auto test tool versioning should match the studio versioning) and the exe contained within that zip is still v10

photo
2

Dear Graham,

Thank you for your feedback. The problem basically is because auto test tool versioning needs to match the studio versioning. Please download the latest version from: https://bizagi.sharefile.com/d-s513bf29a79c427f8

Regards

photo
1

Great, that works fine. Thank you very much.

photo
1

Can you also provide me with the version of the tool to work with v10.6 of Bizagi Studio please?

photo
2

Dear Graham,

Regarding your question, If you want to execute automatic testing tool in v10.6, you can use the 10.7 version which works from Bizagi v10.4 to Bizagi v10.7.

We recommend to use our latest releases. It means to use Bizagi 10.7 and 11 versions.

Regards

photo
1

Thanks a lot

photo
photo
1

We have the same problem, our Bizagi is 10.7.0.2287, the testing tool is 10.7.0.2083.

photo
1

Dear Mark,

Please download again the application according your needs:

11 Version

10.7 Version

Regards

photo
1

Juan, right question, wrong answer...but I found the problem & the fix.

You're right that you need to right tool.

Here's the fix:

- in the App folder, find the .CONFIG file, and put all your project/system parameters in there, then run, all will work.

- when using "Options" to set the parameters, it does not rewrite the .CONFIG file as it should.

We're not using v11 yet, so I don't know if v11 automatic testing tool writes to it's config file properly, or has the same bug as 10.7.

FWIW, clicking options will show you what you put in the config file, the tool simply forgot to write back to the config file when doing a change. So always put your params in the config file.

Cheers!

- Mark

photo