Topic
  • 2 replies
  • Latest Post - ‏2012-12-23T08:12:54Z by SystemAdmin
SystemAdmin
SystemAdmin
1305 Posts

Pinned topic giving values t flag and variable externally at run time and Stub function

‏2012-12-12T05:44:21Z |
Hi,
How can i give these two things in Rhapsody
1.giving the values to flags and variables at simulation(Animation)time which are using for controlling the state flow by using condition connector
2.Writing stub functions (which will give user defined return values) in test conductor.
Currently I am using Rhapsody version 7.6 with test conductor
Updated on 2012-12-23T08:12:54Z at 2012-12-23T08:12:54Z by SystemAdmin
  • pathfinder_hartmut
    pathfinder_hartmut
    49 Posts

    Re: giving values t flag and variable externally at run time and Stub function

    ‏2012-12-12T08:50:47Z  
    Hi U45D_Abdul_Nazar,

    I am not sure that I understood your question entirely.

    The easiest way to test using TestConductor is using sequence diagram TestCases. By defining the return value for an operation call on a TestComponent, TestConductor automatically creates the desired stub operation during update TestCase - this is explained in the user guide pg 66ff.

    For setting values to attributes, you could use TestActions in sequence diagram TestCases (user guide pg 213ff) or, alternatively, you could invoke appropriate setters by the TestContext .

    Regards, Hartmut
  • SystemAdmin
    SystemAdmin
    1305 Posts

    Re: giving values t flag and variable externally at run time and Stub function

    ‏2012-12-23T08:12:54Z  
    Hi U45D_Abdul_Nazar,

    I am not sure that I understood your question entirely.

    The easiest way to test using TestConductor is using sequence diagram TestCases. By defining the return value for an operation call on a TestComponent, TestConductor automatically creates the desired stub operation during update TestCase - this is explained in the user guide pg 66ff.

    For setting values to attributes, you could use TestActions in sequence diagram TestCases (user guide pg 213ff) or, alternatively, you could invoke appropriate setters by the TestContext .

    Regards, Hartmut
    Thanks Hartmut for the reply