Community
Participate
Working Groups
As any NamedElement, a TestCase can be shown (DND from model) in the Requirement diagram. Instead of the Generic representation as a NamedElement a TestCase should have a specific representation (although it should probably not be created in Requirement diagram). TestCase creation is not specific to a particular diagram as any Behavior (or Operation) can be candidate to be a TestCase. A possible support could be obtained with a SysML specific context command that offers to turn supported elements into TestCase (resulting in TestCase stereotype application).
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>>)
