This took quite a long time to solve, but was an enjoyable process.
Shae and I were working on a site where OATS just stopped working. This is a painful thing, as we generally get awesome functional consultants to record the OATS scripts - whether these are load testing or automated regression testing. In general this works, until it does not.
There are always consistent problems - problem 1 - run openscript as admin or you cannot record your scripts - ahh, that old chestnut!
Problem 2 - helpers not installed properly into the browsers, reinstall the helpers - ahh another ripper.
This was different. We'd record scripts and replay them - no problems, but the transactions were not hitting the database. Please note, this is the core purpose of load testing, if you do not reconcile the data change as well as the load testing activity - then you might as well not do it! You must ensure that the transactions are hitting the database when the load testing is running.
OATs is a strange beast, it'll give you the impression of a LOT of success, when it's doing absolutely nothing in the background... Sending and receiving a bunch of 200s -thanks for nothing.
Sample of a lot of "passed" above.
What we found with the JD Edwards correlation library, it was not dealing with stateId properly.
If you goto script properties and look at the JD Edwards load test correlation library:
I needed to disable the last line. The options above are needed, but the correlation library was messing with stateId (not incrementing it) and therefore the changes were not being applied to the database.
Shae came up with another work around and incremented the stateID manually (using the @ functions from the correlation library).
From our research, the @StateIdCount (stoopid name if you ask me). was being used and was always set to 1. When comparing this to the actual execution values, this was set to a 2 on the recorded script.
Looking into the jar file, I was hoping for code, but only got the classes.
"oracle.oats.scripting.modules.jdeLoad.transformRules.JdeTransformRule"
Which are found in the plugins dir.
Fingers crossed that this is going to work for all of the iterations.
I did spend a lot of time creating a cookie for e1AppState which did not make any difference - Doh!
My openScript version:
OpenScript
Version: 13.3.0.1 Build 262
Copyright © 2008, 2018, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
