Hi. We recently extended our entities in a quarkus project with panache to kill all our daos. it all worked very well until we saw that out of the sudden our code coverage dropped about 10%. it even werent classes that have been altered due to the panache extension. we searched a long time for it till we found out that we drop the coverage the moment our entities extend panacheentity. Did you experience anything like that?
Don't worry about that. PanacheEntity ships with the quarkus and is out-of-scope. I wouldn't test the abstract classes just to increase the code coverage.
It actually were service tests for our entity Services. We extended all our entities from the panache entity and all tests dropped to zero in our coverage. After a while we figured that using primitives in our entities caused the problem. Using the object wrappers solved the problem
Quarkus model is plain stupid they have quarkus version of every dependency if they did not provide that for you good luck. It has great features but i don't like this type of things i hope they can create more reasonable solution for it.
The problem is, that an external dependency needs to be compatible to be natively compiled. There are dependencies, that simply do not work (i.e. Frameworks that uses Reflections all over the place). That's why quarkus provided some Libs, that are proven to work.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
Nice, gonna try to use this for one of my private projects.
Hi. We recently extended our entities in a quarkus project with panache to kill all our daos.
it all worked very well until we saw that out of the sudden our code coverage dropped about 10%.
it even werent classes that have been altered due to the panache extension.
we searched a long time for it till we found out that we drop the coverage the moment our entities extend panacheentity.
Did you experience anything like that?
Don't worry about that. PanacheEntity ships with the quarkus and is out-of-scope. I wouldn't test the abstract classes just to increase the code coverage.
It actually were service tests for our entity Services. We extended all our entities from the panache entity and all tests dropped to zero in our coverage.
After a while we figured that using primitives in our entities caused the problem.
Using the object wrappers solved the problem
For once, you have made some persistence stuff, thanks
Quarkus model is plain stupid they have quarkus version of every dependency if they did not provide that for you good luck. It has great features but i don't like this type of things i hope they can create more reasonable solution for it.
The problem is, that an external dependency needs to be compatible to be natively compiled. There are dependencies, that simply do not work (i.e. Frameworks that uses Reflections all over the place). That's why quarkus provided some Libs, that are proven to work.