Skip to content

Latest commit

 

History

History
55 lines (40 loc) · 2.51 KB

testing.md

File metadata and controls

55 lines (40 loc) · 2.51 KB
Raw

Testing

Testing the changes in these libraries is quite complex. The integration_environment folder has a Vagrant/Ansible setup that will set up a test environment for you. This test environment contains 2 hosts:

  • DC01 - Windows domain controller
  • DEBIAN10 - A Linux test host with Docker and the local omi repo copied to ~/omi

Before running the playbook stage you will need to download the GitHub Actions PSWSMan artifact from a run and place it in the same directory as main.yml.

To create this environment, run the following:

cd integration_environment
vagrant up
ansible-playbook main.yml -vv

You can also specify the following --tags to only run a specific component of the main.yml playbook:

  • windows: Setup the Windows domain controller
  • linux: Setup the Debian host
  • build_artifacts: Copy across the GitHub Actions artifact for testing

The domain information and credentials are dependent on the values in integration_environment/inventory.yml. It defaults to a domain called omi.test with the test user omi@OMI.TEST with the password Password01. The environment comes prebuilt to allow you to run the libmi.tests.ps1 Pester tests in various distribution Docker containers. To run tests for all the distributions run the following:

cd integration_environment
ansible-playbook test.yml -vv

# Run the tests for only 1 distribution, add '-e distribution=<distribution>'
ansible-playbook test.yml -vv -e distribution=centos8

If you wish to run more tests manually in the test environment you can log onto the DEBIAN10 host and start up your own test container with:

cd integration_environment
vagrant ssh DEBIAN10

cd ~/omi
./test.py  # Will prompt for the distribution, specify as a positional arg to run automatically

The test.py has the following optional arguments that can be specified:

  • --docker: Sets up a docker container for the distribution selected and runs the tests in there
  • --interactive: When combined with --docker it will open an interactive shell in the test docker container so you can manually run whatever tests you want
  • --output-script: Whether to output the test bash script instead of running it
  • --skip-deps: Don't install the required test dependencies
  • --verify-version: Instead of running the full test suite, this just verifies the library version can be loaded and the versions match the argument value