Running tests fails with AssertionError

[tijuca]

Running the tests while package build in Debian unstable fails since some time with this error message:

> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_test -- --system=custom --test-args="{interpreter} -Wd manage.py test"
> I: pybuild base:232: python3.9 -Wd manage.py test
> Creating test database for alias 'default'...
> System check identified no issues (0 silenced).
> .................................................................................F......................................................................................................................................................................................................................................................................................../usr/lib/python3.9/unittest/case.py:550: DeprecationWarning: Use '__' to separate path components, not '.' in accessor 'a.b' (fallback will be removed in django_tables2 version 3).
>   method()
> ...............
> ======================================================================
> FAIL: test_should_support_custom_dataset_kwargs (tests.test_export.ExportViewTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/<<PKGBUILDDIR>>/tests/test_export.py", line 227, in test_should_support_custom_dataset_kwargs
>     self.assertIn(title, wb.sheetnames)
> AssertionError: 'The Sheet Name' not found in ['-']
> 
> ----------------------------------------------------------------------
> Ran 377 tests in 0.715s
> 
> FAILED (failures=1)
> Destroying test database for alias 'default'...
> E: pybuild pybuild:354: test: plugin custom failed with: exit code=1: python3.9 -Wd manage.py test
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 --system=custom "--test-args={interpreter} -Wd manage.py test" returned exit code 13

The full build log is accessible here http://qa-logs.debian.net/2021/11/04/django-tables_2.4.1-1_unstable.log

The test was previously successful, I expect that some update one ore more other Python packages produces now this error.

[jieter]

I just updated a bunch of requirements, can you test again using master?

[tijuca]

It seems that some depending packages are now working fine together with django-tables2, at least I can't reproduce this issue any more. But I would wait for a new final version before doing a new upload into the Debian archive as the issue was "only" within the tests.

Thanks!