Opened 4 months ago

Last modified 4 months ago

#29308 new Cleanup/optimization

Clarify how assertQuerysetEqual()'s transform parameter works

Reported by: Alexander Todorov Owned by: nobody
Component: Documentation Version: 2.0
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

According to:

Asserts that a queryset qs returns a particular list of values values.

The comparison of the contents of qs and values is performed using the function transform;

The way I read this is that this assert method receives a queryset and a list parameters and compares their contents for equality. By default it will use repr to do that but the user can change this. The way the docs are written suggests that the transform function is applied to both the queryset and the values list. In other words in my tests I can write:

self.assertQuerysetEqual(some_query_taken_from_request_context, [test_object1, test_object2, etc])

The tutorial doesn't use the above but instead hard codes string representations in the tests:

IMO this is less optimal, makes test suites more fragile (dependent on repr()) and less intuitive b/c the expected value isn't a list of the actual objects but a list of their representation which may have been obtained elsewhere.

Note: this may sounds like an RFE but if we trust the docs it's a bug.

Note2: I can contribute a PR for this and update the existing test suite & docs. Just let me know how you feel about it.

Change History (1)

comment:1 Changed 4 months ago by Tim Graham

Component: Testing frameworkDocumentation
Description: modified (diff)
Summary: Testing: assertQuerysetEqual's transform parameter not applied to the values parameterClarify how assertQuerysetEqual()'s transform parameter works
Triage Stage: UnreviewedAccepted
Type: BugCleanup/optimization

As someone who knows how the transform parameter works, the documentation is unclear to me. Changing behavior would be backwards incompatible.

For the use case you mentioned, it would also be useful to recommend assertSequenceEqual(queryset, [obj1, obj2, ...]) and assertCountEqual() as these are simpler than assertQuerysetEqual().

Note: See TracTickets for help on using tickets.
Back to Top