PR#3: Initial example of the Flexible Metadata Format - tests/python

		`@@ -0,0 +1,4 @@`
		`+ contact:`
		`+ - Petr Šplíchal <psplicha@redhat.com>`
		`+ - Miro Hrončok <miro@hroncok.cz>`
churchyard commented 5 years ago mhroncok at redhat.com please
		`+ component: [python]`

smoke/venv.fmf

file added

+49

		`@@ -0,0 +1,49 @@`
		`+ summary: Basic smoke test for virtualenv`
		`+ description: \|`
		`+ Check basic functionality of Python virtual environments (venv`
		`+ or virtualenv based). The test supports different python`
		`+ versions & implementations including pypy and jython.`
		`+`
		`+ The following steps are performed:`
		`+`
		`+ * Create virtual environment`
		`+ * Activate virtual environment`
		`+ * Install pip, pytest and Cython`
		`+ * Create and test a simple module`
		`+ * Check we can do extension modules`
		`+ * Ensure we can test with the tox tool`
		`+`
		`+ Use the following environment variables to adjust what`
		`+ should be tested (default values listed first):`
		`+`
		`+ * VERSION ... python version (3.7, 3.6, 2.7, 2.6)`
		`+ * PYTHON ... implementation (python${VERSION}, pypy, pypy3, jython)`
		`+ * METHOD ... virtual environment creation method (venv, virtualenv)`
		`+ * TOX ... enable or disable the tox test (true, false)`
		`+`
		`+ path: smoke`
		`+ test: ./venv.sh`
		`+`
		`+ tier: 1`
		`+ tags: [venv]`
		`+`
		`+ environment:`
		`+ VERSION: 3.7`
		`+ METHOD: venv`
		`+ TOX: true`
		`+ duration: 10m`
		`+ component+:`
		`+ - python2`
		`+ - python26`
		`+ - python3`
		`+ - python34`
		`+ - python35`
		`+ - python36`
		`+ - pypy`
		`+ - pypy3`
		`+ - jython`
		`+ - python-pip`
		`+ - python-wheel`
		`+ - python-setuptools`
		`+ - python-virtualenv`
		`+ - python-tox`

psss commented 5 years ago

This shows how test metadata could look like with FMF.
https://fedoraproject.org/wiki/Flexible_Metadata_Format

psss commented 5 years ago

@churchyard, could you please have a look whether the description & summary included in the venv.fmf describe well what the test does?

churchyard commented on line 2 of main.fmf 5 years ago

can this be both of us?

churchyard commented on line 6 of smoke/venv.fmf 5 years ago

of Python virtual environments (venv or virtualenv based).

churchyard commented on line 12 of smoke/venv.fmf 5 years ago

pytest and Cython

churchyard commented on line 22 of smoke/venv.fmf 5 years ago

virtual environment creation method (venv, virtualenv)

churchyard commented on line 21 of smoke/venv.fmf 5 years ago

(python${VERSION}, pypy, pypy3, jython)

churchyard commented on line 29 of smoke/venv.fmf 5 years ago

python?

churchyard commented on line 38 of smoke/venv.fmf 5 years ago

what exactly is this? should it list e.g. python3 or python34 or pypy3 as well?

churchyard commented 5 years ago

Added some comments.

1 new commit added

Incorporate pull request feedback

5 years ago

1 new commit added

Update the list of components

5 years ago

psss commented 5 years ago

Thanks for the feedback.

can this be both of us?

Make sense, updated. I'll update the spec as well.

of Python virtual environments (venv or virtualenv based).
pytest and Cython
virtual environment creation method (venv, virtualenv)
(python${VERSION}, pypy, pypy3, jython)

Updated.

python?
what exactly is this? should it list e.g. python3 or python34 or pypy3 as well?

Tags could be used for additional filtering. While the component
field should contain all relevant components. So I would suggest
to keep tags only for further categorization of python tests and
list all components using/affected by this test.

See the following page for details about already drafted/defined
metadata attributes: https://fedoraproject.org/wiki/CI/Metadata

churchyard commented 5 years ago

All components are listed in https://bugzilla.redhat.com/show_bug.cgi?id=1623434