|Re: Remote testing externally built code (native and java) [message #69308 is a reply to message #69288]
||Tue, 02 May 2006 13:34
| Paul Slauenwhite
Registered: July 2009
You can have the TPTP Test execution harnness push the builds to the
target/remote host (identified in the artifact file) or run tests on builds
already on the target/remote host (identified in the location file). TPTP
does not provide support for remote command execution from a test (although
you may configure an application running in the Agent Controller to invoke
remotely). The test is executed on the target/remote host.
"Tim Gourley" <email@example.com> wrote in message
> Hi Randy,
> I was wanting TPTP to push the already built binaries, not invoke the
> (though would invoking the builds be out of the question? this seems like
> remote command execution, with less artifacts to push)
> But not to let my question creep, I initially want to be able to test
> pre-built binaries.
> Thanks all!!!
> "In theory there is no difference between theory and practice. But, in
> practice, there is." - Jan L.A. van de Snepscheut
> "Randy D. Smith" <firstname.lastname@example.org> wrote in message
> >> "Tim Gourley" <email@example.com> wrote in message
> >>>My understanding of TPTP is that:
> >>>* I should be able to distribute these 'staged' builds to remote
> >>> (multiple platforms)
> > Tim, Could you clarify one thing for me? By the above, are you wanting
> > distribute the *results* of "the 'staged' builds" to remote machines?
> > (easy with TPTP's file transfer capability) Or are you wanting TPTP to
> > drive the *building* out on the remote systems?
> > Just curious.
> > --
> > RDS
> > Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
> > Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
Powered by FUDForum
. Page generated in 0.02589 seconds