|
|
|
Re: Start multiple test components [message #36540 is a reply to message #36443] |
Fri, 21 October 2005 13:58 |
No real name Messages: 404 Registered: July 2009 |
Senior Member |
|
|
Hello Holger,
Sorry for the later reply. I got in touch with one of our more experienced
committer on the test component to find out more about remote deployment of
tests before getting back to you. As you have already found out, the
following relations exist in the TPTP test component:
- 1-to-many relationship between artifacts and test suites
- 1-to-many relationship between deployment files and (artifact, location)
pairs
- 1-to-1 relationship between a launch configuration item and a test suite
- 1-to-1 relationship between a launch configuration item and a deployment
file
Although there exists a 1-to-many relationship between deployment files and
(artifact, location) pairs, the current test execution harness that is
included with TPTP will only honor the first entry in the deployment file.
I have to admit that although nothing is fundamentally wrong with this
model, the procedure of setting it up is very cumbersome (as it requires the
user to create three resources: deployment, location, and artifact if they
wish to do a remote deployment). I will open a feature for this to be
followed upon in the future. Unfortunately, because of the radical changes
that the feature will require and the number of resources available, we may
have to delay it for a later release than 4.2.
From the looks of it, you may have to write some code to get what you
exactly want for the remote deployment of a test on multiple machines. As
you have noted below, you will need to write a new launch configuration
wizard that gets rid of the 1-to-1 relationship between a launch item & a
test suite and have it replaced with a 1-to-1 relationship between a launch
item & a deployment file. The test execution harness needs to also be
modified to be able to walk through each (artifact, location) pair entry of
the deployment file and launch them appropriately.
Thanks.
"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
news:dj8cot$349$1@news.eclipse.org...
> Hi Ali,
>
>
>
> Ali Mehregani schrieb:
>
> >Defining a deployment consisting of multiple artifact/location pair
should
> >do the trick. Let us know if you have any problems going with this
> >approach.
> >
> >
> >
> I looked deeper into the source code and the handling of test suites.
>
> I think it's impossible to start more than one Tests at
> once, because a launch configuration is associated with _one_
> Test Suite wich is associated with _one_ deployment.
> So i need to write a new Launch Wizard, right?
>
> The Test Execution Harness always handles _one_ Test Suite, so i need to
> write a new
> LaunchConfigurationDelegate class also.
>
> To gather the results in one Test Suite will be another challenge...
>
>
>
> Conceptually it looks very bad to me, because what i actually
> want is to start _one_ distributed test and not to start multiple
> tests which produces distributed results.
>
>
> Do you think, there is a way to manage it?
>
>
> Thanks
> Holger
>
> >"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
> >news:dj81hi$go2$1@news.eclipse.org...
> >
> >
> >>Hello,
> >>
> >>
> >>I'm looking for a way to start multiple test components on diffrent
> >>
> >>
> >machines to realize a distributed test bed.
> >
> >
> >>I think, it's already supported by defining multiple test asset/test
> >>
> >>
> >location pairs in one deployment.
> >
> >
> >>Or is there a better way?
> >>
> >>
> >>Thanks
> >> Holger
> >>
> >>
> >
> >
> >
> >
|
|
|
Re: Start multiple test components [message #36574 is a reply to message #36443] |
Fri, 21 October 2005 14:10 |
No real name Messages: 404 Registered: July 2009 |
Senior Member |
|
|
Here's the feature: https://bugs.eclipse.org/bugs/show_bug.cgi?id=113350
I've added your email address to the CC list. You're more than welcome to
contribute code, comments, etc... to the report.
"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
news:dj8cot$349$1@news.eclipse.org...
> Hi Ali,
>
>
>
> Ali Mehregani schrieb:
>
> >Defining a deployment consisting of multiple artifact/location pair
should
> >do the trick. Let us know if you have any problems going with this
> >approach.
> >
> >
> >
> I looked deeper into the source code and the handling of test suites.
>
> I think it's impossible to start more than one Tests at
> once, because a launch configuration is associated with _one_
> Test Suite wich is associated with _one_ deployment.
> So i need to write a new Launch Wizard, right?
>
> The Test Execution Harness always handles _one_ Test Suite, so i need to
> write a new
> LaunchConfigurationDelegate class also.
>
> To gather the results in one Test Suite will be another challenge...
>
>
>
> Conceptually it looks very bad to me, because what i actually
> want is to start _one_ distributed test and not to start multiple
> tests which produces distributed results.
>
>
> Do you think, there is a way to manage it?
>
>
> Thanks
> Holger
>
> >"Holger Machens" <machens@informatik.fh-wiesbaden.de> wrote in message
> >news:dj81hi$go2$1@news.eclipse.org...
> >
> >
> >>Hello,
> >>
> >>
> >>I'm looking for a way to start multiple test components on diffrent
> >>
> >>
> >machines to realize a distributed test bed.
> >
> >
> >>I think, it's already supported by defining multiple test asset/test
> >>
> >>
> >location pairs in one deployment.
> >
> >
> >>Or is there a better way?
> >>
> >>
> >>Thanks
> >> Holger
> >>
> >>
> >
> >
> >
> >
|
|
|
Powered by
FUDForum. Page generated in 0.03563 seconds