Testing Interfaces
All of the tests we’ve looked at so far have centered around our resources. This is the most important type of testing because it extends to every interface that uses our resources. If the number 5 is an invalid argument value when calling an action, that property will extend to any UI or API we use to call that action. This doesn’t mean that we shouldn’t test those higher layers.
What it does allow us to do is to be a bit less rigorous in testing these generated interfaces. If we’ve tested every action, validation, and policy at the Ash level, we only need to test some basic interactions at the UI/API level to get the most bang for our buck.
Testing GraphQL
Since AshGraphql is built on top of the excellent absinthe library, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access