On 02/20/2013 01:25 AM, Dan Callaghan wrote:
Excerpts from Dan Callaghan's message of 2013-02-20 14:18:18
+1000:
> Coming soon: my "reference harness" proposal to go along with this
> one...
This is now published:
http://beaker-project.org/dev/proposals/reference-harness.html
It's related to the harness API proposal, in that the reference harness
will use the new API and we will use the harness switching support in
Beaker to test it out. The reference won't require any actual changes to
Beaker itself though, and can be developed completely independently.
Hi Dan,
I was thinking about what you said about not implementing the localhost
xmlrpc interface. I'd like the harness to work independently from
beaker and be able to record results without being tied to beaker too.
The main reason for this is so that when developing tests they
run/execute exactly the same as they would in the automated
environment. When running locally we want the results stored locally,
probably recorded in the recipe.xml.
I don't think we need to implement the localhost xmlrpc interface to get
this behaviour, maybe use local sockets? Any other thoughts?