Robot Framework behaviour

Hi,

We are evaluating different test automation tools in order to replace that one we are currently using. And we think that Robot Framework fits our requirements, but we need to be sure about its full compliance. Please find them hereafter.

  • Access control via LDAP
  • Admin setup
  • User setup
  • User identification via LDAP
  • Account configuration
  • User administration
  • Test project creation / deletion
  • Assign users to test project
  • Test requirements generation from a .csv file
  • Test requirements manual setup
  • Test requirements handling
  • Test requirements register
  • Test cases manual setup
  • Test cases handling
  • Test cases traceability
  • Test cases register
  • Test plan setup
  • Build setup
  • Test case to test plan assignment
  • Test case to user assignment
  • Test result register (Note: Test launching not done from test automation tool)
  • Bug tracking via Mantis BT integration
  • Bug traceability
  • Bug register
  • Test report generation (HTML / Word)
  • Metrics generation (HTML / Excel / Word)
  • Test cases versioning

Hopefully, you can shine a light on it.

Thanks in advance and kind regards.

Hi Florencio,

I suggest you start making a table and then gather data about each topic (point in your list), which robot framework libraries if any can do what you want, and if no libraries available then which python module might help.

Also the answer to many topics may be the same. e.g. This should get you started:

topic comment
* Access control via LDAP
* Admin setup
* User setup
* User identification via LDAP
* Account configuration
* User administration
* Test project creation / deletion
* Assign users to test project
A quick search found robotframework-ldaplibrary, however it seems to be a java library that’s not been updated in a while, so it might only work with jython, which is no longer supported? I’m not familiar with this library.

An alternative might be the python-ldap python module, as long as some one on your team can write a little python they can easily create the custom LDAP keywords you need and the rest of the team can just use them like any other robot keywords
* Test requirements *
* Test cases
* Test plan setup
Build setup
* Test case to test plan assignment
* Test case to user assignment
Metrics generation (HTML / Excel / Word)
These are all features of a test management application, not a test automation tool, you will still need a test management application. the good news is robot framework will integrate with most via the api’s and results published using the xunit file format that you can optionally output from robot framework

When you decide which test management application you want to use ask here on the forum how to intergrate it with robot framework
* Bug tracking via Mantis BT integration
* Bug traceability
* Bug register
The good news is I know the answer to this, Mantis has a rest api, there’s an example here that might help
* Test report generation (HTML / Word) Easy robot frameworks default report is html, however the xunit option might be more interesting if your test management application supports it
* Test cases versioning Version control is normally handled by a version control system, most people use git, but as robot files are plain text they will work well with any version control system.

If you need to do manual versioning (not recommended) then use ether the the tag or metatdata features of robot framework to include the test version number in your test reports

Hope that helps,

Dave.

3 Likes

Hi, Dave,

Thank you very much for your answers. It was a great help.

Kind regards.

1 Like