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

Backend tests should not reuse unique keys. #17478

Closed
1 task
mshima opened this issue Jan 4, 2022 · 1 comment · Fixed by #24748
Closed
1 task

Backend tests should not reuse unique keys. #17478

mshima opened this issue Jan 4, 2022 · 1 comment · Fixed by #24748
Labels
area: enhancement 🔧 $$ bug-bounty $$ https://www.jhipster.tech/bug-bounties/ theme: java $200 https://www.jhipster.tech/bug-bounties/
Milestone

Comments

@mshima
Copy link
Member

mshima commented Jan 4, 2022

Overview of the issue

At spring-boot v2.6.0 migration, reactive mongodb tests started having lots of random backend tests failures.
Those failures look driver related, but we can fix the failures by improving our tests and stop reusing unique keys like login and emails.

See #16787.

JHipster Version(s)

main

JHipster configuration

unrelated

Entity configuration(s) entityName.json files generated in the .jhipster directory

unrelated

Browsers and Operating System

unrelated

  • Checking this box is mandatory (this is just to show you read everything)
@deepu105 deepu105 added $$ bug-bounty $$ https://www.jhipster.tech/bug-bounties/ $200 https://www.jhipster.tech/bug-bounties/ labels Aug 15, 2023
@mshima
Copy link
Member Author

mshima commented Jan 4, 2024

Looks like the underlying driver issues was fixed.
Reactive mongodb tests are passing now.

@deepu105 deepu105 added this to the 8.2.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: enhancement 🔧 $$ bug-bounty $$ https://www.jhipster.tech/bug-bounties/ theme: java $200 https://www.jhipster.tech/bug-bounties/
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants