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

[Slack]- Test Run Summary card can show more details #310

Closed
Vishnuvenu89 opened this issue Jan 29, 2022 · 6 comments
Closed

[Slack]- Test Run Summary card can show more details #310

Vishnuvenu89 opened this issue Jan 29, 2022 · 6 comments

Comments

@Vishnuvenu89
Copy link

Vishnuvenu89 commented Jan 29, 2022

currently test run summary shows below data

We can further customize this by adding below options

Option to show the name of the test suite - Regression/Sanity/Prod Testing - can be set via CourgetteOptions
Also option to send Report(Extent/Allure) as link to slack
image

@mateiQA
Copy link

mateiQA commented Jan 29, 2022

While we are on this subject, maybe allow a setter method for Session ID so that we can chain multiple runners together based on it? For now, I assume, every runner will create a new session id and if you run 2 runners in the same test run via gradle/maven you will get 2 different test summaries. If we could chain them and create a session id from outside (gradle or mvn build scripts) and pass it to the runner classes we could chain multiple test runners as part of the same 'run'. Concrete example: I run 1 test ng runner class for tests that run headless and 1 test ng runner class for tests that run not headless (for specific tests that don't run under headless mode clipboard data validating etc). I assume each runner class would create it's own TestSummary so if it's possible to merge them somehow (via session id) that would be awesome

@prashant-ramcharan
Copy link
Owner

@Vishnuvenu89 I can add a slackTestIdentifier Courgette option in a future release.

With regards to sending a link to slack for allure / extent reports - this link would just be pointing to a local path from the machine executing the tests. As these reports are not published anywhere with a public URL, it doesn't make sense to add a link to slack because no one would be able to open it.

@prashant-ramcharan
Copy link
Owner

@mateiQA In short, this cannot be done.

sessionId is immutable by design and Courgette cannot aggregate and merge results from 2 separate Java processes (i.e. Courgette runners). Results are calculated in memory within each Courgette process so even if we use the same sessionId for multiple Courgette runners, it wouldn't help merge results because one process wouldn't know the results of the other.

@mateiQA
Copy link

mateiQA commented Feb 3, 2022

@mateiQA In short, this cannot be done.

sessionId is immutable by design and Courgette cannot aggregate and merge results from 2 separate Java processes (i.e. Courgette runners). Results are calculated in memory within each Courgette process so even if we use the same sessionId for multiple Courgette runners, it wouldn't help merge results because one process wouldn't know the results of the other.

thanks for the information

@prashant-ramcharan
Copy link
Owner

prashant-ramcharan commented Feb 27, 2022

You can now use Courgette option slackTestId to specify a custom test id / test suite name etc..

@Vishnuvenu89
Copy link
Author

Vishnuvenu89 commented Feb 28, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants