codecov-io
commented
4 years ago Codecov Report
Merging #91 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #91 +/- ##
=======================================
Coverage 88.86% 88.86%
=======================================
Files 4 4
Lines 548 548
=======================================
Hits 487 487
Misses 61 61Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 31bbf27...6b51048. Read the comment docs.
dependabot-preview[bot]
Bumps pytest from 5.2.2 to 5.2.3.
Release notes
*Sourced from [pytest's releases](https://github.com/pytest-dev/pytest/releases).* > ## 5.2.3 > pytest 5.2.3 (2019-11-14) > ========================= > > Bug Fixes > --------- > > - [\#5830](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5830): The > first test in a package (`__init__.py`) marked with > `@pytest.mark.skip` is now correctly skipped. > - [\#6099](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6099): Fix > `--trace` when used with parametrized functions. > - [\#6183](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6183): Using > `request` as a parameter name in `@pytest.mark.parametrize` now > produces a more user-friendly error.Changelog
*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 5.2.3 (2019-11-14) > ========================= > > Bug Fixes > --------- > > - [\#5830](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5830): The first test in a package (`__init__.py`) marked with `@pytest.mark.skip` is now correctly skipped. > - [\#6099](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6099): Fix `--trace` when used with parametrized functions. > - [\#6183](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6183): Using `request` as a parameter name in `@pytest.mark.parametrize` now produces a more user-friendly error.Commits
- [`dd9a27c`](https://github.com/pytest-dev/pytest/commit/dd9a27cf543c39f91039ecd7aa6aa595b3e79330) Adjust CHANGELOG - [`5e8c47f`](https://github.com/pytest-dev/pytest/commit/5e8c47faad91ccf49897a290efd62bcac1971ff7) Preparing release version 5.2.3 - [`92d6a05`](https://github.com/pytest-dev/pytest/commit/92d6a0500b9f528a9adcd6bbcda46ebf9b6baf03) Show a better message when 'request' is used in parametrize ([#6184](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6184)) - [`6f2c0fd`](https://github.com/pytest-dev/pytest/commit/6f2c0fd2e8e8154c8129900c9a1c650068811404) Show a better message when 'request' is used in parametrize - [`55a58bc`](https://github.com/pytest-dev/pytest/commit/55a58bcd3d15887610e1303f4076401bd16ba742) Merge pull request [#6173](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6173) from brettcannon/patch-1 - [`0b40749`](https://github.com/pytest-dev/pytest/commit/0b40749c9826d67ff44044608778d6ccd763e95a) Delineate syntactically that the 'match' argument to 'raises' is keyword-only - [`adccb63`](https://github.com/pytest-dev/pytest/commit/adccb63de01965ff873038fa2b1bacfa7dbaf049) setup.cfg: fix check-manifest ignore [ci skip] ([#6156](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6156)) - [`41604ee`](https://github.com/pytest-dev/pytest/commit/41604eeb3e70c35103b5260b20419a817a0fe6ac) setup.cfg: fix check-manifest ignore [ci skip] - [`85288b5`](https://github.com/pytest-dev/pytest/commit/85288b53218d4e0037dce9c34bd37f86fa9e212d) fix bug with nonskipped first test in package ([#5831](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5831)) - [`5f9db8a`](https://github.com/pytest-dev/pytest/commit/5f9db8a01721e10162769b96b82794dd069bbaeb) Merge pull request [#6138](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6138) from blueyed/ci-py38 - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/5.2.2...5.2.3)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)