ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 21-05-2024 00:07 IST |
Main | My View | View Issues | Change Log | Roadmap | Monitor project |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0007889 | Part-1 Metamodel | [TDL] New Feature | public | 06-12-2019 13:25 | 27-04-2020 14:28 | ||||
Reporter | Andreas Ulrich | ||||||||
Assigned To | Philip Makedonski | ||||||||
Priority | normal | Severity | feature | Reproducibility | have not tried | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | [TDL] Part-1 V1.4.1 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0007889: Dependency specification between test descriptions | ||||||||
Description | So far, test descriptions are specified independently from each other. There are 2 issues with this approach: 1) It is hard to recognise which TD is at top level (i.e., a TD not invoked by another TD) from a set of available TDs and hence will be transitioned to an executable test case. 2) Specifying dependencies among TDs requires another "master" TD at top level, which invokes TDs that are later transitioned to individual test cases. That is, not only the master TD will become an executable test case, but the TDs invoked by this master TD, while the master TD itself will become the control logic of a test campaign to be implemented. A possible solution could be to tag a TD with an attribute denoting TOP or MASTER. Alternatively, an ordering concept among TDs could be proposed. In addition it should be discussed whether all possible operations are allowed in a master TD or whether only a subset shall be supported. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0015528) Philip Makedonski (manager) 16-12-2019 15:37 |
Clarification regarding mapping/dependency between globally ordered to locally ordered test descriptions is needed as well. |
(0015609) Finn Kristoffersen (developer) 31-01-2020 07:34 |
Two options for the resolution of this issue were considered: - introduction of a property to test descriptions to indicate that this is an independent entry point for test execution or - introduction of a predefined annotation type to declare a test description as an entry point for test execution. The latter option has been selected as this only has an implication on processes and tools external to TDL and it has no syntactic implications except for the beyond the use of the predefined annotation. A predefined annotation type "Master" has been introduced and a note added to the Test Description clause. |
Issue History | |||
Date Modified | Username | Field | Change |
06-12-2019 13:25 | Andreas Ulrich | New Issue | |
06-12-2019 13:25 | Andreas Ulrich | Status | new => assigned |
06-12-2019 13:25 | Andreas Ulrich | Assigned To | => Philip Makedonski |
16-12-2019 15:37 | Philip Makedonski | Note Added: 0015528 | |
31-01-2020 07:34 | Finn Kristoffersen | Note Added: 0015609 | |
31-01-2020 07:34 | Finn Kristoffersen | Resolution | open => fixed |
06-02-2020 21:40 | Finn Kristoffersen | Status | assigned => feedback |
27-04-2020 14:28 | Finn Kristoffersen | Status | feedback => resolved |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |