Bug Fixes in ReadyAPI 3.20.2

Applies to ReadyAPI 3.30, last modified on March 24, 2022

In ReadyAPI 3.20.2, the following issues reported by our customers have been fixed:

Overall

  • When you used the high DPI resolution, some dialogs could not fit the screen. (RIA-15921)

ReadyAPI Test

  • The TestComplete test step did not work. (RIA-18682)

  • When you used the All at Once strategy in security scans, only the last parameter was actually tested. (RIA-18835)

  • ReadyAPI looked hanged when it showed big error messages that occurred in Groovy scripts. (RIA-18759)

  • If a test suite name contained special symbols (\, /, :, *, ?, ", <, >, |), ReadyAPI did not create the related JUnit-Style HTML report. (RIA-18739)

  • The Headers panel in the GraphQL test step did not have the context menu, so you could not call the Get Data dialog to specify a property expansion. (RIA-12997)

  • The TestSuiteRunListener.afterRun event listener did not work properly when you ran test suites in parallel. It might result in some test suites being run several times. (RIA-11933, RIA-9350)

ReadyAPI Performance

  • LoadUI Agent posted error messages to the log of several ReadyAPI instances, no matter which instance was executing a load test. (RIA-18465)

  • The Test Case Level metric showed a wrong value. (RIA-18929)

ReadyAPI Virtualization

  • SOAP virtual services could not read WS-Security messages and encode responses to them. (RIA-4699)

See Also

Version History
What's New in ReadyAPI 3.30.0

Highlight search results