Export results from run screen

[damies13]

Export results from run screen

[damies13]

Comment from rohitcav

Also can we get a report in html/excel/word format?

My reply to this:

I had planned to export to a csv/tsv which would be easy to import into excel (issue #17), but i'm in two minds as to whether I should have an intensive reporting functionality within the gui or break it out to a seperate tool like LoadRunner does with LR Analysis? JMeter also seems to take this approach.
FYI - All the results are all stored in an SQLite3 database in the results directory, Also the agents table gives you the agent monitoring data. So if you are comfortable with SQL you can easily create your own custom reports from that, this will also be the data source if I decide to go with an external reporting tool.

[damies13]

At the moment I have functionality built to generate 3 csv files:

• Summary data (as displayed in run screen)
• Raw Data (result data behind the summary)
• Agent Data

With these 3 files you should have everything needed for reporting test results

• these files can import them into excel easily
• with excel Summary data can be nicely formatted as a table
• with excel you can filter the Raw Data for drill down information
• with excel you can create graphs from the Raw Data
• with excel you can create graphs from the Agent Data (e.g. running users)

In addition to this you could also create an odbc connection from excel or another application to query the data for creating graphs and tables.

I have place holder code commented out but ready for html & word format reports which i'll leave as is for now.

[damies13]

CSV export functionality merged into branch v0.4.4

[rohitcav]

Hi Dave,

Apology for delay in response. I was out of office from couple of weeks.
I executed my script with the latest version of rfswarm and agent and it looks good from earlier version.
Just one concern,
In reporting, the result name is very descriptive and long. Even for a login an application the credentials appears in the result name. I would suggest to optimize in result name and not to show such details.
I can see there are lots of improvements in few days.. Keep it up..

One more suggestion: Can we export the result by clicking on the csv icon once test finishes? And also test end time in the console?

[damies13]

Hi rohitcav,

Thanks for the feedback, many of the improvements were as a result of our conversations so your contribution has helped.

Regarding your questions:

Can we export the result by clicking on the csv icon once test finishes?

You can click the csv export at any time, usually you would wait until the test finished and then do the export, but there is nothing to stop you from doing it earlier either. I deliberately chose not to restrict this to after the test finished because this was one of the issues I have had with Loadrunner over the years, many times I have needed to get the results from a test before the end of the test, usually the trigger is something beyond your control.

And also test end time in the console?

I thought I had done that, but when I checked the code, it only happens if you used one of the auto-run modes, I guess I need to implement this for manual run as well. I logged Issue #51 for this.

[rohitcav]

I ran couple of test and waited for more than 30 mins but still test is not getting stopped automatically. However, stats are showing on the table.

[damies13]

Can you show me a screen shot of your plan screen?

[rohitcav]

Here,

[damies13]

Ok, and when you run those tests individually from robot framework how long do they take to complete?

Also at the 30 min mark, on the run screen was the number under Robots 0 or higher than 0? if the robots count is still above 0 the test hasn't finished ramping down and some test cases are still going.

What should be happening based on this plan:

• In the first 20 seconds all 4 tests start
• in the following 40 seconds, if any of these tests finish their first iteration they will start the second iteration (same test repeated for a second time), then 3rd, 4th, 5th etc
• after 60 seconds, no new iterations will be started, but any that are running will be allowed to run to their natural completion.

Because most test cases take longer than 1 minute, especially if you have added think times. But because rfswarm doesn't know how long your test case will run for the ramp down in the plan is estimated based on the ramp-up it could be much longer or much shorter, for example, if your test case takes ~1hr to run then the ramp down will be ~1 hour (minus the run time and some of the ramp up), likewise if your scripts only take 10 minutes and your ramp up was 1 hour, then the ramp down will be ~10 minutes.