Other approach is to create dependency tree for tests (what tests depends
on which code) and CI to run only the impacted tests for the corresponding
code change (refer
http://google-engtools.blogspot.in/2011/06/testing-at-speed-and-scale-of-google.html).
I am not sure how dependency tree will be ma
Hi Ashvin,
The way we're using log markers is to provide an alternative way for
enabling verbose logging beyond just specifying log levels per class or per
package.
Some of our concepts (LRU, TOMBSTONE, DISTRIBUTION, etc) span code that
doesn't follow the same boundaries as classes or packages. I
Hi,
I can use log4j configuration to change log levels by specific packages and
classes. I noticed sizable usable of LogMarkers in the code for additional
filtering. I guess markers are used for cases beyond trace level logging
and across package boundaries. I was wondering if their are any guidel
On Tue, Jun 16, 2015 at 3:13 PM, jun aoki wrote:
> Anthony, thank you for providing the info. It is straightforward while
> developing.
>
> Some of us think we should run all tests (several hours according to Dan)
> and there are good reasons to do so.
> Roman, if you know the answer, please let u
