-
Notifications
You must be signed in to change notification settings - Fork 282
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
ArchUnit performance is too slow to run per maven build #1160
Comments
The
|
Hey, I also thought that, but it’s actually just the first test to run, caching the classes for subsequent tests. If I comment out every test from General, the next class is the slow one taking also around 90secs if you still think its usefull, i can see to make an example project ? Cant give source code for this one sadly enough |
Sorry, I just saw that you already told your project has only 120 classes 🙈 So then 90 sec is definitely way too long and I think you just pull in a lot of classes somehow. If you can create an example project that reproduces this, sure, go for it!
dummy test. If the size of this collection should really just be 120 we can see if maybe a tweak to the automatic resolution behavior could speed things up. |
I put all other tests in comment, only keeping the examine. As result I get, in 80 seconds
So it's a bit more but not a lot. If I now use the
Any downside on doing it this way? What could be causing this issue? My code compiles, so all dependencies are on the classpath I would think? |
Downside could be that you have no/wrong information about classes outside of your project. I.e. the classes that are not directly imported will be stubs, they can miss annotations, superclasses or report a wrong |
I am trying to integrate ArchUnit in our build, where it is ran on every compile as a unit test. This seems to be too slow though, if I look at the current performance. Is there a way to speed things up? For your reference, the project only contains 120 java classes so far, so nothing too big
I am using the following setup:
The text was updated successfully, but these errors were encountered: