pytest

问题 I'm using Pytest to test some SQL queries my team runs programmatically over time. My SQL queries are lists of JSONs - one JSON corresponds to one row of data. I've got a function that diffs the JSON key:value pairs so that we can point to exactly which values are different for a given row. Ideally, I'd output a list of these diffs instead of the standard output of an assert statement, which ends up looking clunky and not-very-useful for the end user. 回答1: Pytest give us the hook pytest

问题 I have installed a self-hosted agent on my local VM, it's connected to azure no issues there. I have a python code on azure DevOps I have installed all the requirements.txt requirements manually into the cmd line of the local VM so that self-hosted agent installed on it doesn't have to install them ( to minimize the build & deployment time) But when I have below code in the YAML file to run pytest cases pipeline is failing because of below error This is my Yaml file trigger: - master

问题 I have installed a self-hosted agent on my local VM, it's connected to azure no issues there. I have a python code on azure DevOps I have installed all the requirements.txt requirements manually into the cmd line of the local VM so that self-hosted agent installed on it doesn't have to install them ( to minimize the build & deployment time) But when I have below code in the YAML file to run pytest cases pipeline is failing because of below error This is my Yaml file trigger: - master

问题 As far as I understood from the documentation about pytest fixture parameterization - it creates copies of the fixture with the given params and thus calls each test which requires this fixture with this different copies. My needs are a little bit different. Suppose there is a fixture: @pytest.fixture def sample_foo(): return Foo(file_path='file/path/test.json') def test1(sample_foo): pass def test2(sample_foo): pass The problem is that test test1 and test2 require the same instance of class

问题 As far as I understood from the documentation about pytest fixture parameterization - it creates copies of the fixture with the given params and thus calls each test which requires this fixture with this different copies. My needs are a little bit different. Suppose there is a fixture: @pytest.fixture def sample_foo(): return Foo(file_path='file/path/test.json') def test1(sample_foo): pass def test2(sample_foo): pass The problem is that test test1 and test2 require the same instance of class

问题 I want to centralize configuration for my tests and it seems like pytest.ini would be the place but im having trouble finding an example/feature for this. For example I have a directory with files my tests might need called "test_resources". this is my structure: ├── pytest.ini ├── myproject │ └── someFunctionsOne │ ├── one.py │ └── two.py └── tests ├── integration │ └── someFunctionsOneTestblah.py ├── test_resources │ ├── sample-data.json │ └── test-data-blahablahb.csv └── unit └──

问题 I want to centralize configuration for my tests and it seems like pytest.ini would be the place but im having trouble finding an example/feature for this. For example I have a directory with files my tests might need called "test_resources". this is my structure: ├── pytest.ini ├── myproject │ └── someFunctionsOne │ ├── one.py │ └── two.py └── tests ├── integration │ └── someFunctionsOneTestblah.py ├── test_resources │ ├── sample-data.json │ └── test-data-blahablahb.csv └── unit └──

问题 I have a Jenkins setup with a pipeline that uses pytest to run some test suites. Sometimes a test fails and sometimes the test environment crashes (random HTTP timeout, external lib error, etc.). The job parses the XML test result but the build is marked as FAILURE as long as pytest returns non-zero. I want Jenkins to get exit code zero from pytest even if there are failed tests but I also want other errors to be marked as failures. Are there any pytest options that can fix this? I found

问题 I have a Jenkins setup with a pipeline that uses pytest to run some test suites. Sometimes a test fails and sometimes the test environment crashes (random HTTP timeout, external lib error, etc.). The job parses the XML test result but the build is marked as FAILURE as long as pytest returns non-zero. I want Jenkins to get exit code zero from pytest even if there are failed tests but I also want other errors to be marked as failures. Are there any pytest options that can fix this? I found

问题 I have a Jenkins setup with a pipeline that uses pytest to run some test suites. Sometimes a test fails and sometimes the test environment crashes (random HTTP timeout, external lib error, etc.). The job parses the XML test result but the build is marked as FAILURE as long as pytest returns non-zero. I want Jenkins to get exit code zero from pytest even if there are failed tests but I also want other errors to be marked as failures. Are there any pytest options that can fix this? I found