Comments (4)
Altering the xml writer so it dumps and releases while updating a xml header by overwriting it would actually resolve the resource issues we currently face with captured output intensive test suites
from pytest.
Given that this would probably be a substantial slowdown for many test suites, we're unlikely to put this in Pytest.
I'd suggest copying this logic to your own hook which will be run after each test function, probably pytest_runtest_makereport
.
from pytest.
Hi, excellent!
In any way that you proceed I'll be waiting and if needing testing the new functionality or workaround.
This will be a very useful improvement for my team since we have quite big tests suites.
Glad to hear your suggestions and comments guys. Thanks in advance.
from pytest.
The topic is not something I'll personally touch
I haven't used junitxml output in almost a decade
from pytest.
Related Issues (20)
- [TODO] Upload JUnit reports to Codecov HOT 4
- No tests are run when PyTest encounters some error condition on some of them HOT 1
- Warn on test arguments with default values? HOT 1
- [8.1.x][8.3.x] `testpaths` not taken into account for initial conftests loading when set through configuration file? HOT 4
- Surprisingly, pytest doesn't collect warnings when importing the package for plugins HOT 4
- Support navigating exceptions chains in pdb
- short test summary and -vv
- --failed-first and --new-first don't play well together
- Please make something working HOT 1
- Enable test cases to be executed in a coroutine manner HOT 1
- pytest collection appears to stall/slow down/jam up when some third-party libraries are used; add function to ignore specific modules HOT 2
- Regression in testdir fixture HOT 11
- Fixture with session scope runs more than once unless placed in conftest.py HOT 4
- Running pytest on a file importing pandas and torch.onnx leads to access violation HOT 4
- Same named test functions in different `Pytester` tests will use the same `tmp_path` location HOT 4
- Errors raised in fixture cleanup is shown to originate from last test in the scope, not a test using the fixture HOT 1
- "@" syntax to read in tests from files doesn't seem to work for parameterized files HOT 1
- Add name property to testsuites element in generated JUnit XML HOT 3
- Adding shard option for distributing multiple nodes HOT 2
- Slashes in parametrization values get turned into backslashes on Windows HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pytest.