|Subject:||Re: [Monotone-devel] Testresult|
|Date:||Tue, 5 Jan 2010 15:25:26 -0800|
On 11/24/2009 1:48 PM, Judson Lester wrote:No. In fact I'm not sure that it's even used much, probably related to what you mentioned below. I think I know a better (more flexible) approach, but it would need new hooks to be added.
Following the bisect thread brought some questions about testresult back
to mind. This was one of the features of monotone that drew me to it,
back around 0.14, and I've never really gotten around to really
implementing testresult in my code projects.
Is there a best practice on using the mtn testresult command?
What would probably work would be a separate branch containing (only?) a file with the list of (test-id, pass/fail) pairs; revisions in this branch could be given an extra cert (because certs are indexable, and this is something you'd use for lookups) indicating which revision the contents refer to, and could maybe have an extra file with information on what version of the testsuite was used (for external testsuites).
Doing it this way would require a new "accept_update(old_revision, new_revision)" hook, and helper functions to allow that hook to look up particular revisions (use 'automate select') and then read the contents of those revisions (use 'automate get_file_of'). (We already have an 'mtn_automate' function that would allow these, except that it will E() on its reentrancy check if called this way.)
Does this seem like a reasonable approach?
|[Prev in Thread]||Current Thread||[Next in Thread]|