Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Uml Testing Profile - ValidationAction(Using CallOperationAction)
Uml Testing Profile - ValidationAction [message #1236440] Mon, 27 January 2014 08:16 Go to next message
Joe I is currently offline Joe IFriend
Messages: 28
Registered: May 2013
Junior Member
Hello,

I would like to use the stereotype ValidationAction from the utp specification, but I have some troubles specifying a CallOperationAction.

ValidationAction is an extension of CallOperationAction with following constraints:
[ 1 ] The operation of the action must be the setVerdict operation from the arbiter interface.
[ 2 ] The target of the action must refer to a classifier realizing the arbiter interface.
[ 3 ] The argument of the action must be an expression evaluating to a Verdict literal.
[ 4 ] Validation actions can only be used in test cases (i.e., a behavior where «TestCase» is applied to the behavior or its specification).

I did the following:
.)Added a new sequence diagram and applied the stereotype TestCase
.)Added a lifeline and created an ActionExecutionSpecification
.)Set the action of the ActionExecutionSpecification with a new CallOperationAction
.)Applied the stereotype ValidationAction on the new CallOperationACtion
Inside the CallOperationAction:
.)Set the operation with the setVerdict operation from the arbiter interface (Constraint 1)
.)Created for the target a new InputPin and set type with a class realizing the arbiter interface (Constraint 2)
.)Added a ValuePin (containing an expression) to the argument section (Constraint 3)

-> But after I hit ok, Papyrus changes all CallOperation settings:
-)The target is changed to a InputPin, which type is the Arbiter interface and not the class realizing the interface
-)The ValuePin in the argument section is replaced with an InputPin, which type is a Verdict, but the expression, containing which verdict I want to set is lost...

Is this a bug or am I misinterpreting how to correctly set the CallOperationAction?

Thanks in advance!

Regards,
Joe

[Updated on: Mon, 27 January 2014 08:20]

Report message to a moderator

Re: Uml Testing Profile - ValidationAction [message #1239681 is a reply to message #1236440] Tue, 04 February 2014 19:54 Go to previous messageGo to next message
Christian Damus is currently offline Christian DamusFriend
Messages: 1206
Registered: July 2009
Location: Canada
Senior Member

Hi, Karl,

I would call that a bug. It's OK for a tool to set up a default
CallOperationAction structure, but not to replace elements that you
went out of your way to configure, yourself.

Cheers,

Christian


On 2014-01-27 08:16:35 +0000, Joe I said:

> Hello,
>
> I would like to use the stereotype ValidationAction from the utp
> specification, but I have some troubles specifying a
> CallOperationAction.
>
> ValidationAction is an extension of CallOperationAction with following
> constraints:
> [ 1 ] The operation of the action must be the setVerdict operation from
> the arbiter interface.
> [ 2 ] The target of the action must refer to a classifier realizing the
> arbiter interface.
> [ 3 ] The argument of the action must be an expression evaluating to a
> Verdict literal.
> [ 4 ] Validation actions can only be used in test cases (i.e., a
> behavior where «TestCase» is applied to the behavior or its
> specification).
>
> I did the following:
> )Added a new sequence diagram and applied the stereotype TestCase
> )Added a lifeline and created an ActionExecutionSpecification
> )Set the action of the ActionExecutionSpecification with a new
> CallOperationAction
> )Applied the stereotype ValidationAction on the new CallOperationACtion
> Inside the CallOperationAction:
> )Set the operation with the setVerdict operation from the arbiter
> interface (Constraint 1)
> )Created for the target a new InputPin and set type with a class
> realizing the arbiter interface (Constraint 2)
> )Added a ValuePin (containing an expression) to the argument section
> (Constraint 3)
>
> -> But after I hit ok, Papyrus changes all CallOperation settings:
> -)The target is changed to a InputPin, which type is the Arbiter
> interface and not the class realizing the interface
> -)The ValuePin in the argument section is replaced with an InputPin,
> which type is a Verdict, but the expression, containing which verdict I
> want to set is lost...
>
> Is this a bug or am I misinterpreting how to correctly set the
> CallOperationAction?
>
> Thanks in advance!
>
> Regards,
> Karl
Re: Uml Testing Profile - ValidationAction [message #1240026 is a reply to message #1239681] Wed, 05 February 2014 15:04 Go to previous message
Joe I is currently offline Joe IFriend
Messages: 28
Registered: May 2013
Junior Member
Thanks for your reply.

I submitted a new bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=427473
Previous Topic:Does Papyrus support template?
Next Topic:What is the lowest version of Eclipse on which Papyrus can be intalled?
Goto Forum:
  


Current Time: Sun Jul 05 21:07:58 GMT 2020

Powered by FUDForum. Page generated in 0.02040 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top