Skip to content
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

e2e tests for managing vsphere virtual machines #23

Merged
merged 7 commits into from
May 6, 2024

Conversation

shellymiron
Copy link
Collaborator

@shellymiron shellymiron commented Apr 21, 2024

This PR present the e2e/molecule tests written by QEs (@smiron @epassaro) to manage e2e flows using the validated content roles. in the future those will run in a proper CI.

Molecule is an ansible-testing framework, that allows to write playbooks to validate/assert expected results of a role output.
The structure of the folder will be as follow:

  • each role has a testing folder, those testing folders called "Molecule scenario"
  • each testing folder will contain: vars, tasks, post_validations and scenario (if needed) folders.
  • post_validations tests can be written as an ansible playbook or as a pytest file (currently written as a playbook).
  • each testing folder/Molecule scenario will run twice (molecule use idempotence mechanism)
  • makefile is created to run the molecule test per scenario including all the necessary dependencies

tests/e2e/molecule/manage_vm/scenarios/update_vm.yml Outdated Show resolved Hide resolved
tests/e2e/molecule/manage_vm/scenarios/update_vm.yml Outdated Show resolved Hide resolved
tests/e2e/molecule/vault_files/eco_vsphere_creds.yml Outdated Show resolved Hide resolved
tests/integration/requirements.yml Outdated Show resolved Hide resolved
@mikemorency mikemorency self-requested a review April 25, 2024 12:40
@bardielle
Copy link
Contributor

Please add a changelog file - the name should start with the PR name

@shellymiron
Copy link
Collaborator Author

shellymiron commented Apr 30, 2024

@bardielle can you check if I added it correctly?

@shellymiron shellymiron force-pushed the provision_vm_test branch 4 times, most recently from 01d2918 to 5443d74 Compare April 30, 2024 14:33
@bardielle
Copy link
Contributor

@shellymiron please rebase on main

@shellymiron shellymiron force-pushed the provision_vm_test branch 2 times, most recently from 5587ea6 to 3529f9e Compare May 5, 2024 11:11
@shellymiron shellymiron force-pushed the provision_vm_test branch from 3529f9e to 368baaa Compare May 5, 2024 11:15
@shellymiron shellymiron force-pushed the provision_vm_test branch from 67747e9 to 3e97417 Compare May 6, 2024 06:24
@bardielle bardielle merged commit b54d02d into redhat-cop:main May 6, 2024
19 checks passed
@shellymiron shellymiron deleted the provision_vm_test branch May 8, 2024 13:34
@shellymiron shellymiron restored the provision_vm_test branch May 8, 2024 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants