Monday, 1 February 2016

OATS functional testing gone wrong

First problem was that I could not run any applications, see below:  This was from openscript, l

image

[1] no title

close window(“@index=’0’”)

Need to run openscript as administrator, and then you do not get this error.

image

I then had another issue that the workspace could not be opened. see file “c:\users\smoir\osworkspace\.metadata\.log”

In this file there were tons of errors, I removed the entire “osworkspace” folder and then openscript started.

Wow, now I can start functional testing.

No comments:

Extending JDE to generative AI