Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » Remote testing externally built code (native and java)
Remote testing externally built code (native and java) [message #69058] Fri, 28 April 2006 20:12 Go to next message
Tim Gourley is currently offline Tim Gourley
Messages: 2
Registered: July 2009
Junior Member
Hi,

I’m 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 #69101 is a reply to message #69058] Mon, 01 May 2006 15:45 Go to previous messageGo to next message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
Hi Tim,
You are correct is your expections. However, when launching native
tests there are some customizations required (see
http://www.eclipse.org/newsportal/article.php?id=1539&gr oup=eclipse.tptp#1539).
By way of a tutorial, see:

1) "Testing Applications Using the Eclipse Test and Performance Tools
Platform" tutorial
( http://www.eclipse.org/tptp/home/documents/conferences/eclip seCon2006/Eclip
seCon_2006_Long_Talk_Paul_Slauenwhite.htm)
2) TPTP JUnit Integration Screencast
( http://www.eclipse.org/tptp/home/documents/tutorials/screenc asts/tptpJunit.
html).
3) Help >> Help Contents >> Testing automatically and manually >> Testing
with JUnit >> Running a JUnit test remotely

Paul
"Tim Gourley" <tim.gourley@ugs.com> wrote in message
news:bb4e278ea75010b9e27cee248f5f98b1$1@www.eclipse.org...
> Hi,
>
> I
Re: Remote testing externally built code (native and java) [message #69188 is a reply to message #69101] Mon, 01 May 2006 16:43 Go to previous messageGo to next message
Randy D. Smith is currently offline Randy D. Smith
Messages: 394
Registered: July 2009
Senior Member
> "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)
Re: Remote testing externally built code (native and java) [message #69228 is a reply to message #69188] Mon, 01 May 2006 17:40 Go to previous messageGo to next message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
To further Randy's comment, test authors do not need to directly handle
deploying test assets (e.g. staged builds). Instead, they are made a
dependency of the test in the TPTP Test Artifact and automatically deployed
with the test to the remote (target) host (using the Agent Controller's file
transfer service).

Paul
"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
Re: Remote testing externally built code (native and java) [message #69288 is a reply to message #69188] Mon, 01 May 2006 19:56 Go to previous messageGo to next message
Tim Gourley is currently offline Tim Gourley
Messages: 2
Registered: July 2009
Junior Member
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
Re: Remote testing externally built code (native and java) [message #69308 is a reply to message #69288] Tue, 02 May 2006 13:34 Go to previous message
Paul Slauenwhite is currently offline Paul Slauenwhite
Messages: 970
Registered: July 2009
Senior Member
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)
>
>
Previous Topic:Code Coverage
Next Topic:Testing webapplications with sessionids
Goto Forum:
  


Current Time: Fri Sep 19 10:06:08 GMT 2014

Powered by FUDForum. Page generated in 0.04060 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software