v1.1.0

This is a Feature Release for rfswarm

Thank you to Patrick (@pkievit86) for your contributions to this release.

New Features in this release

• #104 - Improvements for Reporter
• #105 - Improvements for Reporter
• #106 - Will hopefully help to improve the quality of future releases
• #120 - Improvements for Reporter
• #121 - Improvements for Reporter
• #126 - Will hopefully help prevent problems with tests not running as expected for people

v1.0.3

This is a bug fix release

Issues fixed in this release:

• Issue #136

v1.0.2

This is a bug fix release, special thanks to @pkievit86 and @Reddriver for finding the bugs that made this release possible

Issues fixed in this release:

• Issue #119
• Issue #132
• Issue #134

v1.0.1

This is a bug fix release, special thanks to @ryanrosello-og for finding the bugs that made this release possible

Issues fixed in this release:

• #123
• #128
• #129

v1.0.0

This has been a big release for rfswarm, it was originally marked as v0.9.0 but I decided it was a big enough change to be a 1.0 release.

Significant items in this release:

• New contributor Markus (@vaistomarkus) who provided a bug fix Thanks Markus 👍🏼
• A new reporting tool that allows creation of nice reports for your performance test results in html, word and excel formats.
• The ability to schedule the test start time
• the ability to control when the agent uploads the robot logs back to the manager.

The full details of the release can be seen in the issues linked to the release milestone here: https://github.com/damies13/rfswarm/milestone/15?closed=1

With the addition of the rfswarm Reporter I feel this now a complete performance testing solution, however, that doesn't mean there'll be no more work on it, I expect as people use the tool there will be many more feature requests especially for Reporter, the other components are already quite mature and stable and this is why I felt that it justified being a 1.0.0 release.

v0.8.2

This release is a bug fix release for Milestone v0.8.2 reported by the community, and fixes issues:

• #96 - Issues running the manager
• #97 - Import *.robot which has special character (thai characters) then rfmanager display error
• #98 - Agents require a specific format of the manager endpoint in order to connect

Thank you @plhrja and @castiny for the bug reports.

v0.8.1

This release is a bug fix release for Issue #94 reported by the community.

Thank you @tareked20 for the bug report.

v0.8.0

This release is the release where we exit the pre-release stage, it has all the features I believe are needed to be used effectively for performance testing, though some people have already been using this tool and getting good results which also gives me confidence to remove the pre-release tag.

The most important feature of this release is the graphs for monitoring your test, see the new graphs section of the manager documentation for details on this

The other feature is the about screen, this includes quick links to the documentation, Discord and the issues register, not sure how useful this will be but I feel that it makes the application more complete.

Also included is an enhancement request by @vaghetti to include support for initialization files #90, this was robot functionality I had missed so thanks for bringing this to my attention.

v0.7.1

Bugfix for Issue #88

v0.7.0

This is a feature release with the new feature:
Issue #82 - Time fields should auto convert to formatted time value (HH:MM:SS)

Also the following bug fixes are included in this release:
Issue #83 - Listener file went missing from the agent.
Issue #84 - Useful Variables not available in listener mode
Issue #85 - Inconsistant terminology in rfswarm Users / Robots / vusers

I wasn't planning to address issue #82 as early as this as I didn't think it was a big issue but due to the number of support issues i've had with people entering minutes rather than seconds I pushed up the priority of this issue, hopefully this will make things easier for people.

Issue #3 is still being worked on and will be part of the next feature release, but obviously if you find bugs in this release please report them and i'll try to address them quickly.