4 ms·
It depends on the granularity you write your BUILD files with. You can certainly write a target for each individual test, and track dependencies independently.
by habitue 7y ago
It depends on the granularity you write your BUILD files with. You can certainly write a target for each individual test, and track dependencies independently. In practice, you might glob together all files in a directory and put up with a few extra test runs in exchange for less bookkeeping
- vlovich123 7y agoWhat I was saying is that Google somehow manages to track test dependencies at the source level so globbing wouldn't matter.
- joshuamorton 7y agoFrankly you heard wrong. There isn't anything like this.
- vlovich123 7y agoYeah, I was misremembering the post from ~8 years ago. I was thinking of this https://testing.googleblog.com/2011/06/testing-at-speed-and-scale-of-google.html https://testing.googleblog.com/2011/06/testing-at-speed-and-... and it sounds like they do just use Blaze to keep track of explicitly expressed dependencies.