Ash Framework

Testing Resources

As we discussed earlier, the interfaces to our app all stem from our resource definitions. The code interfaces we define are the only thing external sources know about our app and how it works, so it makes sense that most of our tests will revolve around calling actions and verifying what they do. We’ve already seen a brief example when we wrote our first empty-case test,, and now we’ll write some more.

Testing Actions

Our tests will follow a few guidelines:

• Prefer to use code interfaces when calling actions
• Use the raising “bang” versions of code interfaces in tests
• Avoid using pattern matching to assert the success or failure of actions
• For asserting errors, use Ash.Test.assert_has_error or assert_raise
• Test policies, calculations, ...