Roman,
This should be the function that executes the steps of the test case. In
that case, what would be the "ActionName"?
How many Actions do you normally have?
Kindly correct me if i'm wrong.
On Wed, Feb 25, 2009 at 10:08 PM, Roman Zilber <rzil...@gmail.com> wrote:
> Function gDriver_RunAction(ActionName, ParamTableName, ParamRecordName,
> ParamDescription)
> Dim RC
> Select Case Trim(ActionName)
> Case "LoadEnvironment" RC = gDriver_LoadEnvironment(ParamTableName,
> ParamRecordName)
> Case "ReloadAutomationDB" RC =
> gDB_ReloadAutomationDB(Environment("DB_NAME"), Environment("DB_HOST"))
> Case "TestCaseRunner" RC = gDriver_Runner(ParamTableName,
> Environment("REPORT_INDENTATION") + 1)
> Case "RunTestSuite" RC = gDriver_SuiteRunner(ParamTableName)
>
> ....
>
> End Select
> gDriver_RunAction = RC
> End Function
>
>
> On Wed, Feb 25, 2009 at 7:50 PM, alll fun <swam...@gmail.com> wrote:
>
>> Mike,
>>
>> I can understand your point here. But even if all the actions are
>> converted as functions, how do you perform the steps in the test case?
>> Just to get my question clear, example:
>>
>> Test case -1:
>>
>> step-1: Login
>> step-2: Edit some data
>> step-3: Logoff
>>
>> The above three steps are peformed with functions. Where do you define
>> that the test case-1 should perform these steps?
>> Hope this becomes the actions in QTP.
>>
>>
>> Cheers,
>> Swami
>> On Wed, Feb 25, 2009 at 9:16 PM, Mike Pietsch <m...@mikepietsch.com>wrote:
>>
>>>
>>>
>>> Well you could consolidate all your actions into an external VBS
>>> resource and make each action a function. This alone would cut down a
>>> tremendous amount of execution time. (this is why I personally never
>>> use actions)
>>>
>>> Many people use actions because they can maintain an OR specific to
>>> the action. Should this be the case, you can create dynamically load
>>> OR's. As always it's a series of tradeoffs.
>>>
>>> Mike Pietsch
>>>
>>>
>>> On Feb 25, 2009, at 2:32 PM, alll fun <swam...@gmail.com> wrote:
>>>
>>> > Hello members,
>>> >
>>> > I have scripted about 250 test cases and they all need to be
>>> > executed as a Bunch of scripts. Technically in Batch mode. I have
>>> > one action in QTP for a test case, so there will be 250
>>> > (reusable)actions.
>>> >
>>> > Currently what I'm doing is having one main script named as "Driver
>>> > script" and adding all the 250 actions created afore by "Call to
>>> > Existing action". Getting the name of the action from
>>> > datatable(which is entered manually before starting execution) in a
>>> > variable and use it in "Run Action" statement.
>>> >
>>> > CONS:
>>> > Since the driver script holds the 250 actions, opening, editing
>>> > consumes more time (about 3-5 minutes). This is the reason for which
>>> > I'm looking for some other method.
>>> >
>>> >
>>> > Is there any other method that you guys are using?
>>> > Any suggestion for this is highly appreciated.
>>> >
>>> >
>>> >
>>> > --
>>> > Cheers
>>> > Swami
>>> >
>>> > >
>>>
>>>
>>>
>>
>>
>> --
>> With Thanks and Regards
>> Swaminathan.S.P
>>
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
"QTP - HP Quick Test Professional - Automated Software Testing"
group.
To post to this group, send email to MercuryQTP@googlegroups.com
To unsubscribe from this group, send email to
mercuryqtp+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/MercuryQTP?hl=en
-~----------~----~----~----~------~----~------~--~---
