Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[api] Criar testes unitários para a entidade SealEntity. #606

Open
2 of 3 tasks
saracamilo opened this issue Jan 23, 2025 · 0 comments · May be fixed by #655
Open
2 of 3 tasks

[api] Criar testes unitários para a entidade SealEntity. #606

saracamilo opened this issue Jan 23, 2025 · 0 comments · May be fixed by #655
Assignees

Comments

@saracamilo
Copy link
Member

saracamilo commented Jan 23, 2025

WHAT

Precisamos melhorar nossa cobertura de testes da nossa aplicação. Para isso, temos que criar testes unitários automatizados para a entidade /src/Entity/SealEntity.php cobrindo principalmente os métodos getters e setters.

CHECKLIST

  • Identificar os métodos da entidade SealEntity (getters, setters e outros métodos relevantes, por exemplo, toArray).
  • Criar testes unitários cobrindo os métodos getters (os setters já serão testados ao instanciar e setar os dados da entidade)
  • Testar possíveis cenários de falha.

Link para verificar:

https://app.codecov.io/gh/secultce/aurora/blob/main/src%2FEntity%2FSealEntity.php

@saracamilo saracamilo converted this from a draft issue Jan 23, 2025
@alessandrofeitoza alessandrofeitoza moved this from PRODUCT BACKLOG to SPRINT BACKLOG in Aurora Jan 31, 2025
@Akellymourab Akellymourab self-assigned this Jan 31, 2025
@Akellymourab Akellymourab moved this from SPRINT BACKLOG to IN PROGRESS in Aurora Jan 31, 2025
@Akellymourab Akellymourab linked a pull request Jan 31, 2025 that will close this issue
@Akellymourab Akellymourab moved this from IN PROGRESS to REVIEW in Aurora Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: REVIEW
Development

Successfully merging a pull request may close this issue.

2 participants