| f83be5e4273263df2bb9ef609946b911695b3996 |
|
02-Dec-2011 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Use tasks everywhere.
I still need to smash together the 'Run' and 'Vogar' classes; this is an intermediate step on the way to removing miniguice DI from vogar.
git-svn-id: http://vogar.googlecode.com/svn/trunk@263 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/XmlReportPrinter.java
|
| d9085944c8b6d18628266347c59545abae03ab9c |
|
13-Sep-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Adopt miniguice for dependency injection in vogar. This removes the awful amount of duplication previously necessary to initialize fields.
git-svn-id: http://vogar.googlecode.com/svn/trunk@154 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/XmlReportPrinter.java
|
| 8918b5cafd482363a48e0bc9ae0114028cda7e79 |
|
29-Jun-2010 |
jsharpe@google.com <jsharpe@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Respond to r103 comments.
Some parts that I disagree with:
- I feel like putting all this display logic in AnnotatedOutcome would overstep the bounds of what it's meant to do. Really, it's summarizeOutcomes() that cares how things are displayed, and I'd prefer changes in presentation to be done in there instead of in AnnotatedOutcome.
- I'm intentionally keeping the config file separate from the vogar-dir since the location of the config file is not something that can be specified at the command-line, while the location of the vogar-dir is.
git-svn-id: http://vogar.googlecode.com/svn/trunk@106 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/XmlReportPrinter.java
|
| d806c4c900e08bf04e07b5c564f2f61d8c490731 |
|
23-Jun-2010 |
jsharpe@google.com <jsharpe@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Add test history. Key additions:
* if a --results-dir is specified, compares current run against previous runs saved in that directory
* --record-results saves outcomes to a file-system database (given by --results-dir). Conceptually, this should be done only on the continous build machine, but I can imagine some local uses
* --tag now saves a history for that tag
* --compare-to-tag or --run-tag will compare against the history saved when the tag was created
git-svn-id: http://vogar.googlecode.com/svn/trunk@103 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/XmlReportPrinter.java
|
| 7850f3f3da0099b76f09ed64d23e0a43ba4a5c76 |
|
23-Apr-2010 |
jessewilson@google.com <jessewilson@google.com@aa685c63-decc-881d-cd2b-7fa72aad72e1> |
Initial checkin of vogar!
git-svn-id: http://vogar.googlecode.com/svn/trunk@2 aa685c63-decc-881d-cd2b-7fa72aad72e1
/external/vogar/src/vogar/XmlReportPrinter.java
|