What should be changed in version 1.2? Should library maintenance continue?

kowalpy / Robot-Framework-JMeter-Library

Robot Framework and JMeter integration

16 stars 11 forks source link

What should be changed in version 1.2? Should library maintenance continue? #2

Closed kowalpy closed 6 years ago

kowalpy commented 7 years ago

Changes to be considered:

parsing changed log file format (JMeter >= 3.2)
should library be compatible with file format generated by JMeter < 3.2 (new set of keywords ?)
since JMeter 3.0 there is nice HTML dashboard available, does it even make sense to maintain this library? would anyone still use it having nice HTML report included in JMeter?

Library users please state your opinion as a comment to this issue

banrieen commented 7 years ago

Sorry, I did not follow the question in time . First of all，The library even make sense to maintain, we can use RF maintain the jmeter scripts as testsuites or cases, and test cases are unified and maintained.

I think it is necessary to parsing changed log file format (JMeter >= 3.2), because we can assert the result by keywords such as Analyse Jtl Convert ... , Log the steps or results in RF log.html and report.html

As JMeter < 3.2 no longer needed during testing, it is not import to be compatible.

banrieen commented 7 years ago

We usually like to execute the Jmter command than GUI ，RF provides a more convenient way to organize and manage jmeter test scripts。

kowalpy commented 6 years ago

I'll try to release 2.0 which will be able to parse either >3.2 JMeter or <