Code coverage 100% for front end generated apps

[renanfranca]

Hello everyone,

I want to discuss code coverage in front-end generated apps, which I started in this issue: #10925 (comment). I now understand that implementing detailed tests isn't sustainable in the long run (even the books I'm reading say that).

However, 100% code coverage helps me identify dead code and improve some areas to make the code more efficient with fewer branch possibilities. I would appreciate it if we could decide whether we should exclude implementation detail classes from code coverage or if the plan is to avoid 100% code coverage metrics for front-end generated apps.

I opened this discussion because it will directly impact what I'm currently working on: Vue: add OAuth2 Keycloak authentication, and I don’t want to get stuck due to a lack of clarity on what to do hahahha.

cc: @DamnClin, @pascalgrimaud, @qmonmert, @murdos

Thanks! ;)

[murdos]

@renanfranca : my opinion on the subject is not final yet.
I'm experimenting with the merging for code coverage of unit and component tests for the generator itself in #10950, to see what possibility it could brings.
So expect a later answer :)

[renanfranca]

@murdos : Thank you for taking the time to consider this. I believe the pull request and the associated experiment are quite valuable. For the JHipster Lite generator, I think this approach is not only feasible but also offers a comprehensive solution, especially since it addresses the entire system.

As for the front-end application code generated by the pull request I'm working on—add vue oauth2 keycloak module—I don’t see much opportunity for component tests at the moment, as the feature is provided without any accompanying demonstration code.

That said, I’m planning to add unit tests to the pull request to ensure it passes CI without code coverage issues, which will make it easier to get merged.

Once we all agree on the approach to code coverage in front-end generated apps, I’ll proceed with refactoring the module accordingly.

[renanfranca]

As I work towards a conclusion, I find myself reconsidering and now believe we can disable 100% code coverage for at least the front end. I am currently focused on implementing numerous tests for code details, particularly when developing new modules like JWT Vue and OAuth2 Vue. In these modules, you can not create unit tests that effectively evaluate the behaviors (business rules).