#34657: Testing assertions `assertContains` and `assertInHTML` should output the
haystack on failure
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version:
Severity: Normal | Resolution:
Keywords: HTML, assertions, | Triage Stage: Accepted
testing |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 Natalia Bidart]:
> Tentatively accepting because this is related to the testing framework,
though I'm not 100% sure on procedure whether this specific case needs a
forum post since it's marked as a new feature. I would argue this is a
cleanup/optimization :thinking:
Creating a new setting is always controversial (we already have many of
them) and users can already control it with `maxDiff`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34657#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070188c8b5d5f6-2b55770c-a8f2-4137-a0c0-3daef273d1c4-000000%40eu-central-1.amazonses.com.
