Ilya Etingof 9900ad87da Remove Flask mocking from tests
Do not mock `render_template` in tests. Instead let
Flask producing full response, then inspect returned
JSON object making sure the essential bits are present
in the response as we expect them to.

Change-Id: I76fd18b7e90f7a83f548f564e17559f3c8fedec1
Co-Authored-By: Aija Jaunteva <ajaunteva@gmail.com>
Co-Authored-By: Dmitry Tantsur <divius.inside@gmail.com>
Story: 2002745
Task:  22598
2018-07-04 18:35:45 +02:00
2018-03-22 18:53:14 -04:00
2017-04-06 17:05:16 +01:00
2017-04-06 17:05:16 +01:00
2017-04-03 08:33:46 +00:00
2017-04-06 17:05:16 +01:00
2017-04-06 17:05:16 +01:00
2017-04-06 17:05:16 +01:00
2017-04-06 17:05:16 +01:00
2017-04-06 17:05:16 +01:00
2018-06-06 13:38:19 +02:00
2018-05-17 16:14:45 +02:00
2017-07-19 13:04:56 +02:00
2018-01-08 13:02:05 +00:00
2018-06-15 14:06:47 +00:00

Redfish development tools

This is a set of simple simulation tools aiming at supporting the development and testing of the Redfish protocol implementations and, in particular, Sushy library (https://docs.openstack.org/sushy/).

The package ships two simulators - static Redfish responder and cloud-backed virtual Redfish BMC.

The static Redfish responder is a simple REST API server which responds the same things to client queries. It is effectively read-only.

The virtual Redfish BMC resembles the real Redfish-controlled bare-metal machine to some extent. Some client queries are translated to commands that actually control VM instances simulating bare metal hardware. However some of the Redfish commands just return static content never touching the virtualization backend and, for that matter, virtual Redfish BMC is similar to the static Redfish responser.

Description
A set of tools to support the development and test of the Sushy library
Readme 5 MiB
Languages
Python 100%