Refactor API request specs to use token authentication #4330
Conversation
This commit introduces a new shared context, `with authenticated member`, to standardize authentication in the API request specs. The shared context creates a member, generates an API token using the `Token token=` scheme, and provides authenticated and unauthenticated headers for use in the tests. All API request specs in `spec/requests/api/v1/` have been updated to use this shared context. This includes: * Associating test data with the authenticated member to correctly test authorization scopes. * Updating test expectations to reflect the new scoped behavior of the API endpoints. * Refactoring `create`, `update`, and `delete` tests to use the shared headers for checking authorization rules, making the tests cleaner and more robust.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This change refactors the API request specs to use a consistent token-based authentication method. It introduces a new RSpec shared context to handle the creation of an authenticated member and the generation of API tokens. All relevant spec files have been updated to use this shared context, ensuring that the tests accurately reflect the API's authentication and authorization logic.
PR created automatically by Jules for task 6017957769620388270 started by @CloCkWeRX