Cards — Free Sandbox with GraphQL API
The system is simple, it has very little business logic, it is based on everyday tasks, so it is easy to “understand”. Top up the balance, transfer money to another account – quite logical actions that can be tested without detailed technical specifications.
Yes, in students (the second system, for homework) there is a little more logic and in some places it twists into such knots that wow! But I must admit that this is not necessary for getting to know the API. Rather, it is a reserve for the future, to consider different situations from the point of view of test design. So who knows, maybe I will “discover” the second system someday…
When working with GraphQL, the role model and separation of access rights are very important. Usually this is done via LDAP and all that, but we have a test system, so we took the simple way and emulated roles via headers. This is quite enough to feel out possible limitations that can be imposed on the system in the code.
Well, you have to understand that our TOR is from real life. This is exactly how I gave the TOR to the developer (only instead of confluence there was a Google Doc). Usually, novice testers do not believe that there may be no TOR, or written on the knee. Until they start working))
The TOR is often quite vague, so mine only reflects reality. Well, you can also work on it, the developer did everything! And you can test on such scanty information. So I will gradually tidy up the TOR to make it look nicer, but in general this is quite enough for development / testing.
Well, I think I've told you everything, see the rest in the technical specifications. And also wait for articles on GraphQL, because this is why the maps were released into the public domain – to write training materials on them!
PS – look for more useful articles in my blog tagged “useful”. And useful videos are on my youtube channel
