| Test, artifacts and locations properties [message #72434] |
Wed, 31 May 2006 08:45  |
Eclipse User |
|
|
|
Hi All,
There's something i don't understand well in TPTP design. It deals with
properties. As far as i know, one can set properties on artifacts and
locations. I don't understand why properties are available on artifacts
and not on test suites. Let me explain my point of view: When writing
tests, you need to provide some metadata in order to ease test execution.
Most of these informations are test suite specific and not artifact
specific (which is nothing more than a container for me). So it's really
annoying to not be able to set properties on test suite directly.
Perhaps i didn't get the TPTP properties philosophy and , in this case,
please someone explain to me =). In the other case, is it planned to have
properties on test suites (like test version, target SUT, target SUT
version, etc.) ?
A workaround would be to create an artifact per test suite and to put
properties on this. But it's not really what i want to.
What do you think about it ?
Regards
BQ.
|
|
|
| Re: Test, artifacts and locations properties [message #72843 is a reply to message #72434] |
Thu, 01 June 2006 10:24  |
| Eclipse User |
|
|
|
Hi Bertrand,
Test artifacts are for associating objects such as test suites and
datapools. That is, artifacts make an asset available to a test suite.
This is the same association you want make except for flat property data.
You can associate one or more test suites with one artifact to assign
multiple properties to the test suite(s). In effect, the properties you are
setting on your artifact is the metadata describing the execution of the
associated test suite(s) which sounds like the data that you want to
capture. Do you need to access these properties during test execution?
For an explanation on how properties are used in Locations and Artifacts,
see:
Help >> Help Contents >> Testing applications >> Creating a test deployment
>> Deployment ground rules
Paul
"Bertrand Quenin" <bquenin@axway.com> wrote in message
news:d4cd573ed3b8c90e858f0d51ab4b0d26$1@www.eclipse.org...
> Hi All,
>
> There's something i don't understand well in TPTP design. It deals with
> properties. As far as i know, one can set properties on artifacts and
> locations. I don't understand why properties are available on artifacts
> and not on test suites. Let me explain my point of view: When writing
> tests, you need to provide some metadata in order to ease test execution.
> Most of these informations are test suite specific and not artifact
> specific (which is nothing more than a container for me). So it's really
> annoying to not be able to set properties on test suite directly.
>
> Perhaps i didn't get the TPTP properties philosophy and , in this case,
> please someone explain to me =). In the other case, is it planned to have
> properties on test suites (like test version, target SUT, target SUT
> version, etc.) ?
>
> A workaround would be to create an artifact per test suite and to put
> properties on this. But it's not really what i want to.
>
> What do you think about it ?
>
> Regards
> BQ.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04661 seconds
Home