Also escape shell directive commands for safer variable handling.
none
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
| Path | Packages | |||
|---|---|---|---|---|
| M | docs/source/docker.rst (12 lines) |
| Commit | Tree | Parents | Author | Summary | Date |
|---|---|---|---|---|---|
| 11db3f3813e0 | 1af27f9fbc97 | bd9f435ec64b | Kamil Páral | docker.rst: resultsdb directive now supports file input (Show More…) | Jul 26 2016, 7:43 AM |
| Show First 20 Lines • Show All 100 Lines • ▼ Show 20 Line(s) | 99 | .. code-block:: yaml | |||
|---|---|---|---|---|---|
| 101 | name: httpd_sanity | 101 | name: httpd_sanity | ||
| 102 | 102 | | |||
| 103 | environment: | 103 | environment: | ||
| 104 | rpm: | 104 | rpm: | ||
| 105 | - docker | 105 | - docker | ||
| 106 | 106 | | |||
| 107 | actions: | 107 | actions: | ||
| 108 | - shell: | 108 | - shell: | ||
| 109 | - bash test.sh ${item} ${workdir}/test_output | 109 | - [bash, test.sh, '${item}', '${workdir}/test_output'] | ||
| 110 | | ||||
| 111 | - shell: | | |||
| 112 | - cat ${workdir}/test_output | | |||
| 113 | export: test_results | | |||
| 114 | 110 | | |||
| 115 | - resultsdb: | 111 | - resultsdb: | ||
| 116 | results: ${test_results} | 112 | file: ${workdir}/test_output | ||
| 117 | 113 | | |||
| 118 | 114 | | |||
| 119 | Pytest | 115 | Pytest | ||
| 120 | ====== | 116 | ====== | ||
| 121 | Pytest provides richer coding experience (e.g. fixtures, setup methods, teardown methods etc.) and | 117 | Pytest provides richer coding experience (e.g. fixtures, setup methods, teardown methods etc.) and | ||
| 122 | there are projects that already use pytest for docker image testing. For ease of reusability, | 118 | there are projects that already use pytest for docker image testing. For ease of reusability, | ||
| 123 | Taskotron can run test suites written in pytest. For seamless integration we support xUnit format | 119 | Taskotron can run test suites written in pytest. For seamless integration we support xUnit format | ||
| 124 | to propagate check results further. | 120 | to propagate check results further. | ||
| Show All 32 Lines | 149 | .. code-block:: yaml | |||
| 157 | environment: | 153 | environment: | ||
| 158 | rpm: | 154 | rpm: | ||
| 159 | - docker | 155 | - docker | ||
| 160 | - python2-pytest | 156 | - python2-pytest | ||
| 161 | 157 | | |||
| 162 | actions: | 158 | actions: | ||
| 163 | - shell: | 159 | - shell: | ||
| 164 | - systemctl start docker | 160 | - systemctl start docker | ||
| 165 | - docker pull ${item} | 161 | - [docker, pull, '${item}'] | ||
| 166 | - py.test dockertest.py --junitxml=${artifactsdir}/output.xml | 162 | - [py.test, dockertest.py, '--junitxml=${artifactsdir}/output.xml'] | ||
| 167 | 163 | | |||
| 168 | - xunit: | 164 | - xunit: | ||
| 169 | file: ${artifactsdir}/output.xml | 165 | file: ${artifactsdir}/output.xml | ||
| 170 | aggregation: none | 166 | aggregation: none | ||
| 171 | export: test_results | 167 | export: test_results | ||
| 172 | 168 | | |||
| 173 | - resultsdb: | 169 | - resultsdb: | ||
| 174 | results: ${test_results} | 170 | results: ${test_results} | ||
| 175 | 171 | | |||
| 176 | 172 | | |||
| 177 | Other possibilities | 173 | Other possibilities | ||
| 178 | =================== | 174 | =================== | ||
| 179 | Taskotron is capable of running arbitrary code (e.g. via bash directive) in any language. If you | 175 | Taskotron is capable of running arbitrary code (e.g. via bash directive) in any language. If you | ||
| 180 | cannot choose between shell script and pytest, you can always write your docker tests in any other | 176 | cannot choose between shell script and pytest, you can always write your docker tests in any other | ||
| 181 | language you prefer. Just make sure that the test results are in format we understand -- | 177 | language you prefer. Just make sure that the test results are in format we understand -- | ||
| 182 | :ref:`resultyaml-format` or xUnit. | 178 | :ref:`resultyaml-format` or xUnit. | ||