Forum Discussion
Yesterday I made two changes:
1) I created a new Groovy Script Test Step, and copied and pasted the text from the old test step into the new one, and disabled the old test step. This was just in case somehow the metadata for that original test step had gotten corrupted.
2) I disabled a different Groovy script test step that occurred earlier in the test case, that was always failing.
The next run of the test suite ran OK.
I've installed 1.9 and am running the test now.
What I can say now is that some combination of recreating the Groovy script test step, eliminating the earlier Groovy script test step that really was failing, and going to Ready!API 1.9.0 has at least made the problem go into remission if not fixed it completely.
I'd say that we can declare this "fixed" and I'll re-address the issue if it comes back.