community.general/test/integration/targets/include_import/playbook/validate34.yml

- hosts: testhost2

  tasks:
    - name: Assert that playbook3.yml and playbook4.yml were imported
      assert:
        that:
          - canary_var3 == 'playbook3 imported'
          - canary_var4 == 'playbook4 imported'
      tags:
        - validate
        - validate34
Integration tests for import/include (#33418) * First pass at include_role tests * Reorganize test structure Do all import and include tests in a single target. * Build out more tests and test with linear and free strategy for each type * import_role tests * Set target host for play test * Basic import_playbook tests * Basic import/include_tasks tests * Add recursion test * import_playbook tests * Add import_playbook group_vars test Issue #33177 * Additional group_var tests for import_playbook * Enable recursion test * More work on import_tasks * Run all tests via run.sh, improve conditional tests, add never tag Add never tag to certain failining tests and explicitly skip it for now until #34104 is merged. Some tasks need to remain commented out because they cause the entire play to fail and aren't skippable by tags because they are syntax and/or variable checks. Improve test for whether or not a role was run based on a conditional. Since the [import\|include]_role does not register a variable, use a variable that is set inside a role as a canary test for whether or not the role was run. * Use a fail task rather than trigger a failure via bogus command This should resolve the "unstable" test results. * Import tag tests Fix bug it tests where validate tasks weren't run on tag tests. Add tests for task import/include with tags. * Remove test for playbook group_var inheritance 2018-01-19 17:23:48 +01:00			`- hosts: testhost2`

			`tasks:`
			`- name: Assert that playbook3.yml and playbook4.yml were imported`
			`assert:`
			`that:`
			`- canary_var3 == 'playbook3 imported'`
			`- canary_var4 == 'playbook4 imported'`
			`tags:`
			`- validate`
			`- validate34`