{{ message }}
Repository navigation
Corrige testes que podiam passar sem detectar um erro - #929
Open
wandersonsaint014-hue wants to merge 1 commit into
Open
wandersonsaint014-hue wants to merge 1 commit into
wandersonsaint014-hue wants to merge 1 commit into
Conversation
This branch has not been deployed
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
1 participant
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.
Qual era o problema?
Três testes verificam consultas com código de UF, sigla ou região inválidos. Eles deveriam confirmar que a API responde com erro 404.
Porém, se a API respondesse com sucesso por engano, esses testes também poderiam passar, sem perceber o problema.
O que foi corrigido?
Agora os testes exigem o erro 404 e mantêm as verificações que já existiam sobre a resposta.
Como foi verificado?
O que muda na API?
Nada. A alteração melhora apenas os testes, para que detectem esse tipo de falha no futuro. Não significa que a API esteja apresentando esse erro hoje.