Testing for the Presence of Plugs
Explore how to write effective tests for Phoenix plugs to verify they are called correctly on relevant endpoints. Understand how to handle authentication plugs like ValidateJWT and authorization plugs, ensuring your tests confirm proper error handling and database state preservation under failure conditions.
We'll cover the following...
Defining the test for the presence of plugs
While any basic plugs that we write should be unit-tested, we need to add tests to our test suite to assert that they’re called on every endpoint that’s in the pipeline that includes them. While every Plug is different, in our use case both are run before the controller in the call stack. We only need to test for when things aren’t right. That means that testing multiple endpoints for the presence of the same Plug(s) will start to look a little repetitive because the setup (if it exists) and the assertions will be nearly identical. Often only the endpoint will change. We’ll add two tests to assert the presence of our two plugs.
In the router lib/not_skull_web/router.ex, our update endpoint is in a pipeline that ...