[Notes] [Git][BuildStream/buildstream][master] 3 commits: dev-requirements: pytest-cov==2.6.1 for '--no-cov'

[Angelos Evripiotis <gitlab mg gitlab com>]

Title: GitLab

Angelos Evripiotis pushed to branch master at BuildStream / buildstream

Commits:

• fc3dcec8
  by Angelos Evripiotis at 2019-01-11T16:45:00Z

  dev-requirements: pytest-cov==2.6.1 for '--no-cov'
  
  Bump the version of pytest-cov, so that we pick up the fix for
  the '--no-cov' option breaking in pytest 4.0:
  
      https://github.com/pytest-dev/pytest-cov/pull/230
  
  This was the error you would get prior to this version:
  
      _pytest.warning_types.RemovedInPytest4Warning: config.warn has been
      deprecated, use warnings.warn instead
  
  Although it says 'deprecated', it did result in
  termination with stack trace.
  

• f86b7ff3
  by Angelos Evripiotis at 2019-01-11T16:45:00Z

  contributing: '--last-failed' and '--no-cov' tips
  
  To help new folks get to grips with pytest, add some tips on other
  frequently used features.
  

• d983f231
  by Angelos Evripiotis at 2019-01-11T17:19:06Z

  Merge branch 'aevri/tox_no_cov' into 'master'
  
  pytest-cov==2.6.1, contributing: '--last-failed' and '--no-cov' tips
  
  See merge request BuildStream/buildstream!1059

2 changed files:

• CONTRIBUTING.rst
• requirements/dev-requirements.txt

Changes:

CONTRIBUTING.rst

---

...	...	@@ -1534,6 +1534,10 @@ You can always abort on the first failure by running::
1534	1534
1535	1535	tox -- -x
1536	1536
	1537	+Similarly, you may also be interested in the ``--last-failed`` and
	1538	+``--failed-first`` options as per the
	1539	+`pytest cache <https://docs.pytest.org/en/latest/cache.html>`_ documentation.
	1540	+
1537	1541	If you want to run a specific test or a group of tests, you
1538	1542	can specify a prefix to match. E.g. if you want to run all of
1539	1543	the frontend tests you can do::
...	...	@@ -1545,6 +1549,12 @@ If you wanted to run the test_build_track test within frontend/buildtrack.py you
1545	1549
1546	1550	tox -- tests/frontend/buildtrack.py::test_build_track
1547	1551
	1552	+When running only a few tests, you may find the coverage and timing output
	1553	+excessive, there are options to trim them. Note that coverage step will fail.
	1554	+Here is an example::
	1555	+
	1556	+ tox -- --no-cov --durations=1 tests/frontend/buildtrack.py::test_build_track
	1557	+
1548	1558	We also have a set of slow integration tests that are disabled by
1549	1559	default - you will notice most of them marked with SKIP in the pytest
1550	1560	output. To run them, you can use::

requirements/dev-requirements.txt

---

...	...	@@ -2,7 +2,7 @@ coverage==4.4
2	2	pylint==2.2.2
3	3	pycodestyle==2.4.0
4	4	pytest==4.0.2
5		-pytest-cov==2.6.0
	5	+pytest-cov==2.6.1
6	6	pytest-datafiles==2.0
7	7	pytest-env==0.6.2
8	8	pytest-xdist==1.25.0

—
View it on GitLab.
You're receiving this email because of your account on gitlab.com. If you'd like to receive fewer emails, you can adjust your notification settings.