Robot Framework test suite for Python unittest framework
Project description
Python unittest test suite for Robot Framework
This is an experimental package for wrapping Robot Framework test suites into Python unittest suites to make it possible to run Robot Framework tests as plone.testing’s layered test suites:
import unittest2 as unittest
from plone.testing import layered
from robotsuite import RobotTestSuite
from my_package.testing import ACCEPTANCE_TESTING
def test_suite():
suite = unittest.TestSuite()
suite.addTests([
layered(RobotTestSuite('mysuite.txt'),
layer=ACCEPTANCE_TESTING),
])
return suite
RobotTestSuite splits Robot Framework test suites into separate unittest test cases so that Robot will be run once for every test case in every test suite parsed from the given Robot Framework test suite. Because of that, each Robot will generate a separate test report for each test. Each report will have it’s own folder, which are created recursively reflecting the structure of the given test suite.
RobotTestSuite’s way of wrapping tests into unittest’s test suite is similar to how doctest-module’s DocTestSuite does its wrappings.
The main motivation behind this package is to make Robot Framework support existing test fixtures and test isolation when testing Plone. Yet, this should help anyone wanting to use Robot Framework with zope.testrunner or other Python unittest compatible test runner.
If this works for you, please contribute at: http://github.com/collective/robotsuite/
Changelog
1.3.1 (2013-06-03)
Pin robotframework < 2.8rc1, because robotsuite is not yet compatible with robotframework 2.8.x [Asko Soukka]
1.3.0 (2013-04-09)
Allow passing arguments critical/noncritical to only raise an AssertionError if the test is critical [reinhardt]
1.2.2 (2013-04-08)
Fix to copy all screenshots (not only selenium-screenshot*.png) when mergin test reports
1.2.1 (2013-03-08)
Revert setting the default zope.testrunner level and support setting it via environment variable ROBOTSUITE_LEVEL (e.g. ROBOTSUITE_LEVEL=2).
1.2.0 (2013-03-08)
Override test suite __module__ test case id() to support collective.xmltestreport
Add support for zope.testrunner test suite levels (with default value of 2 to allow easily to run all but robot tests with zope.testrunner
1.1.0 (2013-02-20)
Change of behavior to not remove existing robot_output.xml, but always just merge new test data into it. robot_output.xml can be reseted by deleting it manually between tests.
1.0.4 (2013-02-19)
Fix issue in merging of test reports from tests form two or more separate test suites
1.0.3 (2013-02-18)
Fix the example test to read ZSERVER_PORT -environment variable properly
1.0.2 (2013-02-09)
Fix to replace spaces in test report folder names
1.0.1 (2013-02-09)
Add newline before stdout dump on failing tests
1.0.0 (2013-02-08)
Stop replacing spaces with underscores in testnames
0.9.0 (2012-09-21)
Added injecting logged errors into captured stdout to be dumped with robot output when a test fails.
0.8.0 (2012-09-13)
Added support for setting pybot cli-variables from ROBOT_-prefixed environment variables.
0.7.0 (2012-09-11)
Implemented custom merge for Robot Framework reports to create better concatenated test report and fully support Robot Framework plugin for Jenkins.
Fixed to copy (selenium-)screenshots into the root test directory to make it easier to publish them in Jenkins.
0.6.0 (2012-08-21)
Fixed screenshot paths in concatenated report.
Fixed test names to include suite filename instead of classname.
Fixed to allow dash in normalized test names.
0.5.0 (2012-07-23)
Included robotframework test tags as part of tests’ string representation to allow test be filtered with tags (e.g. with zope.testrunner).
Added creation of concatenated log file.
0.4.0 (2012-06-04)
Fixed to rename test method of each test after the actual robot framework test run by the test case.
0.3.1 (2012-06-03)
Updated README.
0.3.0 (2012-06-03)
Enabled robotframework reports for tests. Each test suite and each test will have their own outputdir, recursively.
0.2.0 (2012-06-02)
Support for directories as (recursive) suites.
0.1.0 (2012-05-30)
Proof of concept.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
