On 2 December 2014 at 18:10, Shawn Heisey <[email protected]> wrote: > The test dependency tree for this particular class is *EXTENSIVE* and > not very easy to track down.
How about a black box approach? Run each test individually once with a debugging interface enabled and the code that records every class load and every file system access. That's very similar to what JRebel does. Each test run is a Solr document. The loaded classes/files are multivalued fields. Dump into standalone Solr. Then, when the file changes, search by it's name/location and get back the list of tests that ever touched it. There are some complications due to randomised tests and also due to changed code possibly invoking new code path, but the core idea could probably be prototyped in a day or so to see if it has legts. Regards, Alex. Personal: http://www.outerthoughts.com/ and @arafalov Solr resources and newsletter: http://www.solr-start.com/ and @solrstart Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
