Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
jestdotty4528213dsounds like a nightmare
I'm a fan of subdividing things into self-contained libraries -
2 minutes is okay local, approx 50ms per test... but 20 minutes is too long for pipeline! it's a pain to wait!
if they're truly unit tests, you should be able to parallelize them (most runners do that automatically nowadays, but could depend on what language / framework you're using....) -
junners498212dThis should depend on the pipeline runner configuration. Unit test locally uses your local compute. I.e. your ram and your processor. Your pipeline runner would have a different configuration from your local.
-
NoToJavaScript4647206d@fullstackcircus that's why in local it's so fat. 12 cores ;p In azure pipeline it only runs 2 tests at a time at most
-
NoToJavaScript4647206d@fullstackcircus the thing is, some of them are "too" testy
For example, let's say you have a method on a controller which will check acces rights / role and than call internal service
What you would expect in unit test : Check if service is called. That's all (Via mock)
What's hapening : The service is actuallty called and whole code executed, even if this method has another specific unit test. Basiclly it executes a bit too much.
Related Rants
Is it slow ?
taliking about unit tests. I have 2746 unit tests in a project (Covering around 15% of code).
It takes around 2 minutes in local (With good PC) and aroubnd 20 minutes in a pipeline to execute.
Would you people say it's slow ?
rant
question