webdriverio - I wanted to show all 5 test cases id in the allure report. Should I call beforetest and aftertest five-time - webdriver

I have merged 5 test cases into a single test script in webdriver.io
After execution allure report captured the first test case id only.
As covered purpose, I wanted to show that all 5 test cases id in the allure report.
Should I call beforetest and aftertest five-time. if yes then how can I call ?

Related

Iterating test case in robot framework

I have a test case and i have to iterate the test case no.of times.is there any way we can iterate the test case?
Signin-Personal-Account
[Tags] Tvh2
Given Number of users signs in to their respective devices ${xyz}
Then xyz sees that Sign in is successful
When xyz signs out from the device
Then xyz sees that sign out was successful
And Signin is repeated for 5 times for Ellie```
Test has to repeat 5 times. how to make test case iterate no.of times?
This can be achieved using for loop:
*** Test cases ***
Multiple sign in test
:FOR ${index} IN RANGE 5
\ Signin-Personal-Account
*** Keywords ***
Signin-Personal-Account
[Tags] Tvh2
Given Number of users signs in to their respective devices ${xyz}
Then xyz sees that Sign in is successful
When xyz signs out from the device
Then xyz sees that sign out was successful
Make sure to check the syntax for FOR loop based on the version of robot framework you are using - FOR loop syntax

Acumatica:Tabular Report generates unexpected lines when calling as sub report

Using Acumatica report designer, I've designed a tabular report to fetch one field from SOShiplinesplit.The report's main parameters are RefNbr and ShipLineNbr. If run the tabular report individually, for 1 doc's 1 shipline,its result looks like below:
Tabular Report results when running individually
However, if I add this tabular as a subreport like below,
Add Tabular report as a subreport at ShiplineNbr group level
I met with confusing results if I run the master report to call tabular report
Run within master report
Could anyone give me a hand to get out of this trouble?

UFT - Running a single test case in QTP but a part of the flow needs to be iterated multiple times

I am trying to automate a test scenario using UFT 14.0, where I am using excel to store my test data and using ADODB concept to fetch the test data.
I need to run a single flow from start to end, and in between, a part of the flow needs to be iterated with different sets of data.
Eg: I need to login to makemytrip.com, book a ticket for 10 person with their personal details and then log out. So login happens once, but booking the ticket needs to be iterated 10 times and with different set of data and then finally we logout. I have 2 sheets in test data , first sheet
has login details, the other sheet contains passengers details. How can it be achieved using excel multiple rows concept??
Thanks in Advance. :)
Running a single test flow in QTP but a part of the flow needs to be iterated multiple times
You can iterate the record set obtained from the query. For example :
For i=0 to objRecordset.recordcount -1
testData1= objRecordset.fields(Colname1)
testData2= objRecordset.fields(Colname2)
testData3= objRecordset.fields(Colname3)
'Perform required acitions
objRecordset.movenext
Next
Hope this helps.
Regards,
Sandeep Jaju

Visual FoxPro report total pages

I am able to get the total pages by doing steps as below:
REPORT FORM report NoConsole
lnMaxPages = _PAGENO
REPORT FORM report PREVIEW
but above only work if my report are all in the same group.
Let say I am printing 3 different reports (3 groups), and assuming each group have different pages. How do I display the correct lnMaxPages for each group?
Edit: I am using VFP 5 where there is no _pagetotal command.
You can write a UDF that stores the number of pages (use a variable in the report that only increments for each group) for example, the page number you are on when you are in group 1/2 or 3. Do some math and calculate the number of pages for each group. This will get you the variables when you run it noconsole. Display it on the report when you actually run it to the screen or printer.

create control-M job on the fly

Is it possible to dynamically create control-M jobs.
Here's what I want to do:
I want to create two jobs. First one I call a discovery job, the second one I call a template job.
The discovery job runs against some database and comes back with an array of parameters. I then want to start the template job for each element in the returned array passing in that element as a parameter. So if the discovery job returned [a1,a2,a3] I want to start the template job 3 times, first one with parameter a1, second with parameter a2 and third one with parameter a3.
Only when each of the template jobs finish successfully should the discovery job show as completed successfully. If one of the template job instances fails I should be able to manually retry that one instance and when it succeeds the Discovery job should become successful.
Is this possible ? And if so, how should this be done ?
Between the various components of Control-M this is possible.
The originating job will have an On/Do tab - this can perform subsequent actions based on the output of the first job. This can be set to work in various ways but it basically works on the principle of "do x if y happens". The 'y' can be job status (ok or not) exit code (0 or not) or text string in standard output (e.g. "system wants you to run 3 more jobs"). The 'x' can be a whole list of things too - demand in a job, add a specific condition, set variables.
You should check out the Auto Edit variables (I think they've changed the name of these in the latest versions) but these are your user defined variables (use the ctmvar utility to define/alter these). The variables can be defined for a specific job only or across your whole system.
If you don't get the degree of control you want then the next step would be to use the ctmcreate utility - this allows full on-the-fly job definition.
You can do it and the way I found that worked was to loop through a create script which then plugs in your variable name from your look-up. You can then do the same for the job number by using a counter to generate a job name such as adhoc0001, adhoc0002, etc. What I have done is to create n number of adhoc jobs as required by the query, order them into a new group and then once the group is complete send the downstream conditions on. If one fails then you can re-run it as normal. I use ctmcreate -input_file . Which works a treat.

Resources