Repository navigation
Adiciona cenário de atualização com token inválido (TC-013) - #7
Merged
Merged
Conversation
Diferente do TC-008 (token ausente), aqui o token existe mas é lixo/inválido. Validei manualmente contra a API real que PATCH e DELETE se comportam da mesma forma (403), então o cenário cobre só o PUT pra não triplicar um caso já comprovado equivalente.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
O que mudou
TC-013emupdate_booking.feature: PUT com um token inválido (não ausente, um valor qualquer). Confirmei manualmente contra a API real que o retorno é 403, igual ao caso de token ausente (TC-008) — mas é uma classe de equivalência diferente (token existe e é rejeitado, vs. nenhum token enviado), vale testar separadamente.que ele possui um token de autenticação inválido.docs/test-cases.md) e marker nopyproject.tomlatualizados..featureexplicando por que não repetimos o mesmo caso para PATCH/DELETE (validei manualmente que o comportamento é o mesmo, 403 nos dois).Plano de teste
pytest -m TC-013) contra a API real: passoupytestcompleto,ruff check .,ruff format --check .,mypy .: todos passando