| Remote testing externally built code (native and java) [message #69058] |
Fri, 28 April 2006 16:12  |
Eclipse User |
|
|
|
Hi,
Im very new to TPTP and I am working on a multi-platform distributed
product that would greatly benefit from automated and remote testing.
Our builds would still have to be controlled by an external system, but
the output of the builds can be staged in a common location.
The build artifacts consist of jars, native executables and shared
libraries.
Test code consists of junits, and native executables.
My understanding of TPTP is that:
* I should be able to distribute these staged builds to remote machines
(multiple platforms)
* I should be able to remote execute junit tests and gather results.
(usual junit reports)
* I should be able to remote execute native (test) executables and report
results (stdout/stderr)
I was wondering if someone could tell me if my expectations are reasonable
given current TPTP functionality?
Would someone be so kind as to give me a coarse outline of the steps I
would need to follow to actually make this happen?
Are there already tutorials that go over something like this?
Thanks so much in advance!!!
Regards,
Tim
"In theory there is no difference between theory and practice. But, in
practice, there is." - Jan L.A. van de Snepscheut
|
|
|
|
|
|
|
| Re: Remote testing externally built code (native and java) [message #69308 is a reply to message #69288] |
Tue, 02 May 2006 09:34  |
| Eclipse User |
|
|
|
Hi Tim,
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.
Paul
"Tim Gourley" <tim.gourley@ugs.com> wrote in message
news:e35p5i$k4b$1@utils.eclipse.org...
> Hi Randy,
>
> I was wanting TPTP to push the already built binaries, not invoke the
> builds.
>
> (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!!!
>
>
>
> Regards,
> Tim
>
> "In theory there is no difference between theory and practice. But, in
> practice, there is." - Jan L.A. van de Snepscheut
>
>
> "Randy D. Smith" <randy.d.smith@intel.com> wrote in message
> news:e35dru$5jn$1@utils.eclipse.org...
> >> "Tim Gourley" <tim.gourley@ugs.com> wrote in message
> >>>
> >>>My understanding of TPTP is that:
> >>>* I should be able to distribute these 'staged' builds to remote
machines
> >>> (multiple platforms)
> >
> > Tim, Could you clarify one thing for me? By the above, are you wanting
to
> > 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.67057 seconds
Home