Forum Discussion

Stalsy's avatar
Stalsy
Contributor
3 years ago
Solved

Ready API 3.6.0 Testing for HTTP 405

To Test HTTP 405 - Method Not Allowed I have created a new resource for each API.  These resources are identical to the original APIs but if the original is a GET the "405" new resource is a POST and...
  • richie's avatar
    richie
    3 years ago
    Hey Stalsy,

    If youve set the APIs up in ReadyAPI! as im guessing you have then this is is a known defect with ReadyAPI! It mightve been fixedin a more recent version, but i stumbled across this issue a while back in about v3.3

    If you setup the requests with different methods, but within the same service (so the sibling requests of the same service), then youll see the behaviour youve noticed.

    Setup the different requests in separate services and this will sort your problem.

    Im on my phone rightnow so cant add screenshots. Try and follow the above instructions and if youre still not clear, reply back and i'll add screenshots to help explain.

    Cheers,

    Rich
Stalsy's avatar
Stalsy
Contributor
3 years ago

How does everyone else test HTTP 405 using ReadyAPI?

  • richie's avatar
    richie
    Community Hero
    3 years ago
    Hey Stalsy,

    If youve set the APIs up in ReadyAPI! as im guessing you have then this is is a known defect with ReadyAPI! It mightve been fixedin a more recent version, but i stumbled across this issue a while back in about v3.3

    If you setup the requests with different methods, but within the same service (so the sibling requests of the same service), then youll see the behaviour youve noticed.

    Setup the different requests in separate services and this will sort your problem.

    Im on my phone rightnow so cant add screenshots. Try and follow the above instructions and if youre still not clear, reply back and i'll add screenshots to help explain.

    Cheers,

    Rich
    • Stalsy's avatar
      Stalsy
      Contributor
      3 years ago

      Thanks Rich,

      it's a lot of husslse as I have 7 APIs and two environments, but it worked!

      I created a new service 'ALL405s', set up the end-points and authentication for each environment for the new service,  and cloned every request from the original service to the new one.  Then of course I had to replace in every HTTP405 test case the 'Rest Request' step from the original service to the one from the 'ALL405s'.

      All good now.

      Thank you again