-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Improve integration tests by including more entities configurations #199
Comments
JasonTypesCodes
added a commit
that referenced
this issue
Dec 3, 2020
JasonTypesCodes
added a commit
that referenced
this issue
Dec 4, 2020
JasonTypesCodes
added a commit
that referenced
this issue
Dec 4, 2020
This was referenced Jan 20, 2021
atomfrede
pushed a commit
that referenced
this issue
Jan 22, 2021
* Adds more entity types to CI (#199) * Replaces old ApiModel and ApiModelProperty Swagger annotations with v3 Schema (#199) * Fixes enum issues identified adding more entity examples (#199) * Updates UserResourceIT to have the same create/delete API as other EntityResourceIT tests * Renames BankAccount relationship so that relationship table doesn't collide with entity table * Print a warning when tests are unable to delete enitites * Temporarily commenting out 'with jpaDerivedIdentifier'
As suggested by @JasonTypesCodes let's close this and add more concrete issues if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the feature request
As shown with the last 2 issues I reported - #198 and #197 - the entity generator is not well tested.
We should test various options: service, relationship, pagination, different field types, ...
IMO we should pick some very relevant entity samples in main generator (https://github.com/jhipster/generator-jhipster/tree/main/test-integration/samples/.jhipster) such as
EntityWith*
andFieldTest*
ones.Motivation for or Use Case
Working generated code in various configurations.
Related issues or PR
#198
#197
The text was updated successfully, but these errors were encountered: