-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make end2end tests run against a mocked environment #413
Comments
Initial analysis shows that create_hmc_session() only supports real HMCs, because it dos not create FakedSession objects for mocked HMCs. However, since |
Note: Removal of session IDs in the mocked Logoff operation and validation of session IDs in any mocked operations that require to be logged on has not been implemented in this change. That would require passing the HTTP header fields to the mock support, which is not the case today and would require larger changes. However, since addition/removal/validation of session IDs is implemented for the FakedHmc class, this should be sufficient to provide the session ID support required for zhmcclient/zhmccli#413. Details: * Added support for dynamically creating a session ID in the mocked Logon operation (i.e. _urihandler.SessionsHandler). * The new session ID is stored in the zhmcclient_mock.FakedHmc object in new support for adding, removing and validating session IDs. * Added unit test cases for the session ID support in the zhmcclient_mock.FakedHmc class. Signed-off-by: Andreas Maier <maiera@de.ibm.com>
Note: Removal of session IDs in the mocked Logoff operation and validation of session IDs in any mocked operations that require to be logged on has not been implemented in this change. That would require passing the HTTP header fields to the mock support, which is not the case today and would require larger changes. However, since addition/removal/validation of session IDs is implemented for the FakedHmc class, this should be sufficient to provide the session ID support required for zhmcclient/zhmccli#413. Details: * Added support for dynamically creating a session ID in the mocked Logon operation (i.e. _urihandler.SessionsHandler). * The new session ID is stored in the zhmcclient_mock.FakedHmc object in new support for adding, removing and validating session IDs. * Added unit test cases for the session ID support in the zhmcclient_mock.FakedHmc class. Signed-off-by: Andreas Maier <maiera@de.ibm.com>
Note: Removal of session IDs in the mocked Logoff operation and validation of session IDs in any mocked operations that require to be logged on has not been implemented in this change. That would require passing the HTTP header fields to the mock support, which is not the case today and would require larger changes. However, since addition/removal/validation of session IDs is implemented for the FakedHmc class, this should be sufficient to provide the session ID support required for zhmcclient/zhmccli#413. Details: * Added support for dynamically creating a session ID in the mocked Logon operation (i.e. _urihandler.SessionsHandler). * The new session ID is stored in the zhmcclient_mock.FakedHmc object in new support for adding, removing and validating session IDs. * Added unit test cases for the session ID support in the zhmcclient_mock.FakedHmc class. Signed-off-by: Andreas Maier <maiera@de.ibm.com>
PR zhmcclient/python-zhmcclient#1456 targeted for zhmcclient 1.15.0 provides dynamically created session IDs, and the ability in the |
With PR #411 , the following error is surfaced (using a locally defined mock file, on Python 3.9 on macOS):
The text was updated successfully, but these errors were encountered: