Javier Buzzi comments

Results 148 comments of


                                            Javier Buzzi

Attempt to make codecov less important

@webknjaz what am i missing from the codecov report, the summed up report vs individual ^ (see comment above)

Attempt to make codecov less important

@webknjaz ?

Attempt to make codecov less important

@webknjaz [this is why](https://github.com/pytest-dev/pytest-django/actions/runs/16937568450/job/47997777345?pr=1230) i want to remove codecov most of the time it works. but it always breaks in the most inopportune times...

Attempt to make codecov less important

@webknjaz from my understanding is that the token is expiring because the upload is taking long [randomly] [see how it normally takes 2s](https://github.com/pytest-dev/pytest-django/actions/runs/16937568450/job/47997777311?pr=1230#step:9:1) vs [how it took 4m32s](https://github.com/pytest-dev/pytest-django/actions/runs/16937568450/job/47997777345?pr=1230#step:9:307) -- and...

Attempt to make codecov less important

Maybe.. not ruling that out. But i dont think its the token itself either, otherwise all of the other test steps would fail -- but yes, your guess is as...

Exposes the underlining TestCase instance to avoid using "asserts" module

@bluetech thoughts?

Exposes the underlining TestCase instance to avoid using "asserts" module

> But I think it better to avoid adding new ones. This makes sense. > find a way to make the assert "bind" to the test it is running under....

Exposes the underlining TestCase instance to avoid using "asserts" module

@bluetech what do you think of this approach?

Exposes the underlining TestCase instance to avoid using "asserts" module

@bluetech thoughts how I can improve this?

Exposes the underlining TestCase instance to avoid using "asserts" module

@adamchainz understand the making the fixture name smaller, but not sure about how the wrapper would work without frame hacking.. can you provide an example?