Forum Discussion

mogranovitch's avatar
mogranovitch
Occasional Contributor
4 years ago

Using GraphQL without ability to point to a schema file

Guys,   I have a problem to create a project that would work with multiple GraphQL API's in different environments - using ReadyAPI 3.5.1. I can run individual GraphQL test requests fine with hard...
  • NBorovykh's avatar
    NBorovykh
    4 years ago

    Hi Mikhail,

     

    Thank you for the clarifications.

    I'm afraid there is no much I can suggest for testing your scenario in ReadyAPI before GraphQL introspection (and auto-updating the cached schema) is supported. 

    I've already relayed this to the Product Team so that they could consider these GraphQL support improvements for future versions.

     

     

mogranovitch's avatar
mogranovitch
Occasional Contributor

Hi NBorovyh, Natalie,

 

Thank you for your reply to my question.

 

For #1 - that is unfortunate since other tools I'm using doing that (read schema with provided end point and security token) fine.

For #2 - Few comments:

  1. I'm dealing with multiple sub-systems that do not provide access to their schemas to me and without that I cannot create API and therefore I'm unable to change end-points for each environment as you suggested.
  2. Even if I had access to their schema it would be a huge maintenance nightmare for me to track if any changes are done for any of the schemas - again, this info is not available for me.

Best regards,

Mikhail

NBorovykh's avatar
NBorovykh
Moderator
4 years ago

Hi Mikhail,

 

Thank you for the clarifications.

I'm afraid there is no much I can suggest for testing your scenario in ReadyAPI before GraphQL introspection (and auto-updating the cached schema) is supported. 

I've already relayed this to the Product Team so that they could consider these GraphQL support improvements for future versions.