背景描述

最近才开始了解项目，正在看文档，中文的文档在访问的时候会出现无法访问情况。简单查了一下服务好像不在国内

重点描述遇到的问题：在国内访问文档不稳定

期望的功能特性

期望 文档服务器在国内可以有镜像

When inside the internal shell the cursor-up key just selects the lines in history with no (apparent) useful function.

It would be nice if it could instead access the history (as does ctrl-p/n).

https://github.com/Arkq/flake8-requirements

On the configuration page in the documentation (https://pytest-cov.readthedocs.io/en/latest/config.html) it specifies how to omit tests/* from coverage reporting.

Following the instructions exactly results in tests/* still being covered.

I always use autospec=True in when patching objects. I think this helps to uncover bad mock calls.

Perhaps it would be nice to be able to set this as a default value. E.g.:

def pytest_configure(mocker_config):
    mocker_config.default_autospec = True

I think this FAQ is misleading:
https://pytest-django.readthedocs.io/en/latest/faq.html#how-can-i-use-manage-py-test-with-pytest-django

It says "It translates some of Django's test command option to pytest's" in the docstring.
However, using this example and trying to pass an arg such as keepdb, you get manage.py test: error: unrecognized arguments: --keepdb

For the example to work, us

I think we originally used stevedore because there was little/no documentation about pluggy, now there is actually documentation and its used by more projects

Hi there,

I'm trying to figure out what the numbers in parentheses outputted for each stat value in the table mean.

Looking at the code it seems like its happening over here : https://github.com/ionelmc/pytest-benchmark/blob/2ed70632a38909ced0935c010b6696679a28c412/src/pytest_benchmark/table.py#L39

I'm not sure what pos/total means and what I should gleam from those values in the parent

Test file

import logging
import pytest

@pytest.fixture
def fixture():
    logging.warning('Warning in fixture')


def test_nothing(fixture):
    pass

Output with pytest-sugar

$ pytest -r P test.py 
Test session starts (platform: darwin, Python 3.8.2, pytest 5.3.5, pytest-sugar 0.9.2)
rootdir: /Users/ods/work/sugar-dup-log
plugins: sugar-0.9.2
co

Based on #32 and discussion with @Hultner

• Have a smaller quickstart
• Link to docs in the top of the page (not only badge)
• Move documentation content to a separate document
• Share roadmap info
• Examples of errors that could be found
• Possible workflows for Schemathesis. As a part of a test suite, CI step, CLI, etc
• [Usage](https://github.com/untitaker/

Based on the text at the bottom of https://docs.coveralls.io/supported-ci-services, my understanding is to use Coveralls with an unsupported CI provider, you need to set the other service_* parameters in https://docs.coveralls.io/api-reference.

There doesn't currently appear to be a way to do this though which is preventing me from using this project.

Could,

Could you add more comments to the code and Readme files so that we can better understand the type of objects and the attributes of the following parameters :

• report
• prefix
• summary
• postfix
• cells
• data

I found them in the following hookers:

• def pytest_html_report_title(report):
• def pytest_html_results_summary(prefix, summary, postfix):
• def pytest_html_results_

The variable output_timeout is now a hardcoded constant:

https://github.com/computationalmodelling/nbval/blob/232d2496a01a5a5c96fe98b27977ae5505a15f5e/nbval/plugin.py#L336

For testing large outputs, such as notebook widgets, the 5 seconds are not sufficient.
Making the variable configurable would solve that issue.

Allure report doesn't contain parameters from Scenario Outline

Feature: Some Feature
Scenario: Some Scenario
Given variable is <a_value>
When we add <b_value>
Then the result will be <c_value>

Examples:
| a_value | b_value | c_value |
| 2 | 3 | 5 |
| 3 | 3 | 6 |

The data from "Exambles" doesn't pass to allure repor

See https://kapeli.com/docsets. This pkg might provide a quick means to generate the docset: https://pypi.org/project/sphinxcontrib-dashbuilder/

To reproduce it, run pytest in this repo:

tests/test_pytest_picked.py: 13 tests with warnings
  /home/ana/workspace/pytest-picked/venv/lib/python3.8/site-packages/pytest-5.4.1-py3.8.egg/_pytest/terminal.py:287: PytestDeprecationWarning: TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw instead at your own risk.
  See https://docs.pytest.org/en/latest/deprecation

A quick suggestion for the docs. I'm new to Python for Qt and wasn't sure whether pytest-qt or Qt Test was best for starting out my tests or how the two were related.

Then I saw this blurb from the Qt World Summit website:

Both PySide and PyQt allow rapid prototyping and development of Qt

The contributing guidelines say, "please ensure the coverage at least stays the same before you submit a pull request," but there is no coverage reporting when running the tests with "tox". Looks like "coverage" was removed from the requirements in 0bdbaa805e5e5c334d35accf1341e3f74fa33d15.

(also, btw: the flake8 tox environment fails because flake8 isn't installed.)

It would be useful to add some sort of unique token or phrase somewhere in devtools/ (where users are unlikely to extensively change or delete things) to better track deployments of cookiecutter-cms on GitHub.

For example:

def main():
    set_python_version()
    # Initialise git repo
    os.system('git init')
    # Install dependencies
    os.system('pipenv install --dev')
    # Setup pre-commit and pre-push hooks
    os.system('pipenv run pre-commit install -t pre-commit')
    os.system('pipenv run pre-commit install -t pre-push')
    print(SUCCESS + "Project successfully initiali