Skip to content
This repository has been archived by the owner on Feb 7, 2023. It is now read-only.

i-s-t repetitiveness #298

Open
ashcrow opened this issue Dec 19, 2017 · 3 comments
Open

i-s-t repetitiveness #298

ashcrow opened this issue Dec 19, 2017 · 3 comments

Comments

@ashcrow
Copy link
Contributor

ashcrow commented Dec 19, 2017

There is some repetitiveness in the i-s-t suite. Consider moving things which are done multiple times into their own role OR playbook which gets included more than once.

@miabbott
Copy link
Collaborator

Definitely not doubting you here, but could you provide an example that stuck out to you?

@ashcrow
Copy link
Contributor Author

ashcrow commented Dec 19, 2017

Sure. Quick example:

    # Compare 'atomic host status' and 'rpm-ostree status' again
    - role: atomic_host_status_verify
      stop_daemon: true
      tags:
        - atomic_host_status_verify

    # Re-subscribe
    - role: redhat_subscription
      when: ansible_distribution == 'RedHat'
      tags:
        - redhat_subscription

    # Verify correct SELinux labels again
    - role: selinux_verify
      tags:
        - selinux_verify

Instead of doing the same sets 2x they could be part of one test suite role.

@ashcrow
Copy link
Contributor Author

ashcrow commented Dec 19, 2017

Not the worst thing in the world at all. One could also say that it's easier to read by being explicit like it is today. I just wanted to call it out. By switching to suites run by a playbook you could make it less verbose.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants