Skip to content

Latest commit

 

History

History
36 lines (23 loc) · 1.57 KB

TESTING.MD

File metadata and controls

36 lines (23 loc) · 1.57 KB
Raw

Testing Mesosphere DC/OS Ansible Roles

Our Ansible roles are accompanied by molecule test cases. Both local tests with Vagrant/Virtualbox as well as EC2 instances are used. There are some role specific cases in their roles respective molecule/ director and a global suite that runs all roles from a single unified playbook by installing full clusers.

Example

# pyenv to 3.6
pip install -r test_requirements.txt
cp group_vars/all/dcos.yaml.example group_vars/all/dcos.yaml
molecule test --scenario-name ec2_centos7

Testing Matrix

Generally this project tries to strictly test the Ansible roles functionality, not features or behaviour of DC/OS itself. As a rule of thumb: If a roles main.yml tasks successfuly execute (e.g. no errors), its considered 'good'.

i. OS

CentOS current stable plus its EL variant (as per Mesosphere version policy). Depending on upstream OS release cycles, also upcoming versions as part of (beta) testing.

ii. Infrastrucuture / Provider

  • AWS EC2
  • Vagrant/Virtualbox

iii. DC/OS version

Following the Mesosphere version policy: 1.13, 1.12, 1.11 currently. Depending on release cycles, also the current beta version.

iv. DC/OS live cycle

  • ivA. the initial install
  • ivB. upgrading of a clusters (all node types) and same-version-config-updates
  • ivC. running against an up-to-date cluster with no changes expected, this is covered by molecules build-in idempotency checks