#7 Use "how" to define test step implementation
Merged 5 years ago by psss. Opened 5 years ago by psss.

file modified
+2 -2
@@ -3,7 +3,7 @@ 

      /essential:

          summary: Essential rpmdiff tests (used for gating)

          execute:

-             tool: rpmdiff

+             how: rpmdiff

              tests:

                  - ABI symbols

                  - File permissions
@@ -13,7 +13,7 @@ 

      /additional:

          summary: Additional rpmdiff tests (informational)

          execute:

-             tool: rpmdiff

+             how: rpmdiff

              tests:

                  - File list

                  - Specfile checks

file modified
+5 -5
@@ -4,7 +4,7 @@ 

          # Standard Test Inteface

          /sti:

              execute:

-                 tool: sti

+                 how: sti

                  playbooks:

                      - 'tests.yml'

                  tags:
@@ -12,7 +12,7 @@ 

          # Simple shell script

          /shell:

              execute:

-                 tool: shell

+                 how: shell

                  path: 'tests'

                  test: './test.sh'

                  environment:
@@ -20,13 +20,13 @@ 

          # Workflow Tomorrow

          /wow:

              execute:

-                 tool: wow

+                 how: wow

                  options: '--plan 1234 --tags Tier1'

          # Flexible Metadata Format + Restraint

          /fmf:

              discover:

-                 tool: fmf

+                 how: fmf

                  filter: 'tier: 1, 2'

                  repository: https://src.fedoraproject.org/tests/python

              execute:

-                 tool: restraint

+                 how: restraint

file modified
+2 -2
@@ -2,7 +2,7 @@ 

  /test:

      # Discover relevant tests

      discover:

-         tool: fmf

+         how: fmf

      # System requirements

      provision:

          memory:
@@ -15,7 +15,7 @@ 

              - 'setup.yml'

      # Test execution

      execute:

-         tool: restraint

+         how: restraint

      # Result reporting

      report:

          contact: email@address.org

Let's use "how" to define how each test step is implemented. This
attribute name quite naturally answers questions such as: How to
discover relevant tests? How to provision the system and prepare
it? How to execute tests and how to report the results?

Metadata Update from @psss:
- Pull-request tagged with: ci
- Request assigned

5 years ago

Pull-Request has been merged by psss

5 years ago