Forum Discussion
elenal
7 years agoOccasional Contributor
Seems like it's a problem with ReadyAPI 2.2.0
Rolled back to ReadyAPI 2.1.0 and everything works perfectly. Raised a support ticket with SmartBear
Related Content
- 9 months agosreedhar854385
Seems like it's a problem with ReadyAPI 2.2.0
Rolled back to ReadyAPI 2.1.0 and everything works perfectly. Raised a support ticket with SmartBear