-
Notifications
You must be signed in to change notification settings - Fork 4
Playwright/integration test console #1752
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
Conversation
08875ab to
980f218
Compare
388298f to
9f8d5a7
Compare
9d8a95c to
e31501b
Compare
e31501b to
2184de6
Compare
f801dfe to
aadf71d
Compare
b7aba27 to
f60b1ea
Compare
|
🤖 Hey ! The security scan report for the current pull request is available here. |
f60b1ea to
98b40e8
Compare
54b0f0e to
b4c01ea
Compare
b4c01ea to
24e84a3
Compare
StephaneTrebel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On devrait considérer la création d'un playwright.config.integration.ts qui ciblerait tes tests d'intégration dans un dossier integration-tests qui serait à côté de e2e-tests (et donc avoir deux exécutions de tests playwright dans le package.json)
À rediscuter avec @mathieulaude et @iliesmrf , je pense 😉
24e84a3 to
e294bab
Compare
e294bab to
92abe0f
Compare
StephaneTrebel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM dans l'ensemble 🚀
| /* All timeouts are in milliseconds */ | ||
| // Timeout for each and every `test` block | ||
| timeout: 30_000, | ||
| timeout: Number(process.env.CONSOLE_GLOBAL_TIMEOUT) || 30_000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| timeout: Number(process.env.CONSOLE_GLOBAL_TIMEOUT) || 30_000, | |
| timeout: 30_000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c'est surtout pour concentrer l'usage des CONSOLE_xxx_TIMEOUT sur leur cible, à savoir les tests d'intégration.
Mais si tu veux garder ça comme ça car on peut en avoir besoin pour les E2E c'est fine by me 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comme t'es ok pour les laisser au cas où, je vais les laisser pour ne pas avoir à relancer toute la pipeline x)
| // Timeout for each and every `expect` command | ||
| expect: { | ||
| timeout: 10_000, | ||
| timeout: Number(process.env.CONSOLE_EXPECT_TIMEOUT) || 10_000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| timeout: Number(process.env.CONSOLE_EXPECT_TIMEOUT) || 10_000, | |
| timeout: 10_000, |
Issues liées
Issues numéro: cloud-pi-native/socle#611
Quel est le comportement actuel ?
We don't have integration tests for our Console.
Quel est le nouveau comportement ?
Add integrations tests for Console.
Cette PR introduit-elle un breaking change ?
No.
Autres informations
No.