Vendor-facing API for registration of interop-compliance
Go to file
Michael Krotscheck 240d101539 Added PhantomJS test execution
This patch adds test execution in the headless phantomjs runner, a
feature requested by package maintainers during the summit (for all
javascript projects, not refstack explicitly). The phantomjs
requirement has been explicitly added, as at this point there are
several upstream changes pending inside of npm that would make
this build brittle.

1- NPMv3 will no longer automatically install peerDependencies.
2- karma-phantomjs-launcher will soon gracefully degrade to a
system-installed phantomjs if it is not otherwise available.

Once both of these land we can remove the explicit reference to
PhantomJS.

Change-Id: I054792c23e1f38538800c901605a032118184925
2015-06-05 08:12:59 -07:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
defcore Remove files that are now mastered in openstack/defcore 2015-04-20 17:55:40 -05:00
doc Update readme files with the latest information. 2015-04-30 10:08:58 -07:00
etc Add API endpoint for retrieving capabilities 2015-05-01 11:56:27 -07:00
refstack Fix unit tests failing gate 2015-06-01 11:59:40 -07:00
refstack-ui Added PhantomJS test execution 2015-06-05 08:12:59 -07:00
specs Add Test Records Retrieval API to Refstack v1 API. 2015-03-24 16:03:39 -07:00
.bowerrc Consolidated project files. 2015-06-05 08:12:19 -07:00
.eslintignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.eslintrc Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitreview Add a gitreview setup 2014-05-18 19:02:40 +02:00
.testr.conf Repair tests coverage utility 2015-03-19 10:58:51 +03:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
README.rst Updated the README.rst to fix the link to the wiki page. 2015-05-27 11:12:09 -05:00
__init__.py py33 tests fixed 2014-07-22 09:37:21 +00:00
bower.json Consolidated project files. 2015-06-05 08:12:19 -07:00
package.json Added PhantomJS test execution 2015-06-05 08:12:59 -07:00
requirements.txt Add API endpoint for retrieving capabilities 2015-05-01 11:56:27 -07:00
setup-mysql-tests.sh Improve database creation for testing 2015-03-06 10:14:04 +03:00
setup.cfg Add config auto generator 2015-02-09 11:31:06 +04:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Add API endpoint for retrieving capabilities 2015-05-01 11:56:27 -07:00
tox.ini Add unit tests for untested code 2015-03-19 10:58:51 +03:00

README.rst

refstack

What is refstack?

  • Toolset for testing interoperability between OpenStack clouds.
  • Database backed website supporting collection and publication of Community Test results for OpenStack.
  • User interface to display individual test run results.

Overview

refstack intends on being THE source of tools for interoperability testing of OpenStack clouds.

refstack provides users in the OpenStack community with a Tempest wrapper, refstack-client, that helps to verify interoperability of their cloud with other OpenStack clouds. It does so by validating any cloud implementation against the OpenStack Tempest API tests.

refstack and DefCore - The prototypical use case for refstack provides the DefCore Committee the tools for vendors and other users to run API tests against their clouds to provide the DefCore committee with a reliable overview of what APIs and capabilities are being used in the marketplace. This will help to guide the DefCore-defined capabilities and help ensure interoperability across the entire OpenStack ecosystem. It can also be used to validate clouds against existing DefCore capability lists, giving you assurance that your cloud faithfully implements OpenStack standards.

Value Add for Vendors - Vendors can use refstack to demonstrate that their distros, and/or their customers' installed clouds remain with OpenStack after their software has been incorporated into the distro or cloud.

refstack consists of two parts:

Get involved!