[WIP] Adiciona Github Actions para rodar os testes #75
Conversation
This file contains 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
And transform it from a Model to a infrastructure component. Also make every method responsible of opening and closing the database connection, since it's safer this way.
* Works with ES6 modules * Works with Next.js Absolute Paths
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/tabnews/tabnews/8cvAsof7EPNqK7pM7dWLriETQHqV |
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.
Closes: #74 (PR anterior onde explico o ambiente de testes local)
Closes: #62 (Issue relacionada da Milestone)
Foi uma aventura perceber como o ambiente em que se roda o Github Actions é diferente do meu ambiente local aqui :)
wait-onfunciona localmente que é uma maravilha, mas quebra no ambiente do Github Actions. Eu tava ficando quase maluco tentando isolar o problema de todas as formas e finalmente esbarrei nessa issue. Removi ela das dependências.axiosse demonstra bugado na última versão0.21.1conforme essa issue e tive que voltar para versão0.19.0. Como essa versão tem falha de segurança, movi ela para as dependências de desenvolvimento até a próxima versão sair.wait-on, porque essa lib falava que tal url ainda não estava disponível, mas por dentro do container fazendocurlela estava normalmente.jestcom a flag--forceExit. Mais para frente vou investigar.