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

Not able to generate the Report & Unwanted run statements printing in console - Latest version of serenity #3346

Closed
santhoshkumar-ponnusamy opened this issue Dec 5, 2023 · 10 comments

Comments

@santhoshkumar-ponnusamy
Copy link

Hi @wakaleo & Team,

After upgrading to latest serenity version, am facing 2 different issues, can you please help me resolve this.

Issue 1. Unwanted run status is displaying in console. For example: Run 88: PASS and so on.. How to avoid this.?

image

Issue 2. I am not able to generate the report, getting below error in console. How to resolve this.?

image

@wakaleo
Copy link
Member

wakaleo commented Dec 5, 2023

Try running with -e

@wakaleo
Copy link
Member

wakaleo commented Dec 5, 2023

The first issue looks like an issue with your tests.

@santhoshkumar-ponnusamy
Copy link
Author

Try running with -e

Sorry i didn't understand @wakaleo..

@santhoshkumar-ponnusamy
Copy link
Author

santhoshkumar-ponnusamy commented Dec 5, 2023

The first issue looks like an issue with your tests.

yes, some element mismatch... but for each and every steps why am getting Run 80: PASS, Run 81: PASS statements in console.?

@wakaleo
Copy link
Member

wakaleo commented Dec 5, 2023

I don't think the "Run 80: PASS" statements are related to Serenity.

@santhoshkumar-ponnusamy
Copy link
Author

I don't think the "Run 80: PASS" statements are related to Serenity.

ok... I will check with other forums... Any update on second issue reported.?

@wakaleo
Copy link
Member

wakaleo commented Dec 5, 2023

Run mvn verify -e to see if there is any additional information.

@santhoshkumar-ponnusamy
Copy link
Author

Run mvn verify -e to see if there is any additional information.

Executed using above commans, getting below error.. @wakaleo

image

@wakaleo
Copy link
Member

wakaleo commented Dec 11, 2023

That's an error in the report generation but without a detailed stack trace and/or a project that reproduces the issue, it isn't possible to see where the error is coming from.

@santhoshkumar-ponnusamy
Copy link
Author

Resolved

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

2 participants