| Summary: | [SysML 1.4][Requirement] TestCase should be shown with a specific representation | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Yann Tanguy <yann.tanguy> |
| Component: | SysML | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | Benoit Maggi <benoit.maggi> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | benoit.maggi, klaas.gadeyne |
| Version: | 0.7.0 | ||
| Target Milestone: | 0.11.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 315780 | ||
|
Description
Yann Tanguy
Or one could allow to create it in a Requirement Diagram, but use a extra window that allows to select the 'base element' which is extended by the TestCase stereotype? @Klaas: Did you find the specific Testcase representation in the norm? AFAICT, there is no specific representation besides the obligatory "<<testcase>>". The "challenge" rather seems to be to create an efficient dialog in which the user can select the type of (non-abstract) behaviour (activity, statemachine) or operation that he wants to stereotype, depending on the diagram context. In 0.11.0 there is no popup but a stack in the requirement palette that provide concrete implementation for <<TestCase>> Representation of most test case is a Rectangle with <<TestCase>> written (for operation, the operation name is suffixed by <<testCase>>) |