Repository navigation
chore: adiciona o script npm run test:smoke - #61
Merged
Merged
Conversation
A tag @smoke existia (TC-007, TC-009 e TC-012), mas rodá-la exigia montar o comando do Cucumber na mão. O script dá uma checagem rápida antes de abrir um PR. O CI continua rodando a suíte completa em todo PR, para nenhuma regressão fora da smoke escapar antes do merge.
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.
Problema
A tag
@smokemarca os fluxos mais críticos (TC-007 checkout, TC-009 cadastro e TC-012 login), mas não havia um script para rodá-los. O README mandava montar o comando na mão (npx cucumber-js --tags @smoke).Solução
npm run test:smoke(cucumber-js --tags @smoke), para uma checagem rápida antes de abrir um PR.docs/test-cases.mdpassam a citar o script.O CI continua igual, rodando a suíte completa em todo PR. A smoke cobre 3 dos 43 cenários. Se ela substituísse a suíte nos PRs, uma regressão fora desses 3 só seria pega depois do merge, e a suíte completa leva poucos minutos.
Verificação
npm run test:smokeem modo headless, sem retry: 3 cenários passaram em cerca de 22 s.