djangocms-simple-admin-style 2.1.1

What the tests do

tests/test_selector_coverage.py

Renders a sample of real admin pages and asserts that every rule in the stylesheet still matches something. When a new Django release renames or restructures admin markup, this names the exact rules that stopped applying instead of leaving you to spot it in a screenshot – the failure mode that produced ol.breadcrumbs, .titles-and-tools and [aria-current="page"].

tests/test_stylesheet_sanity.py

Structural checks needing no rendered HTML, over both stylesheets. Most usefully, it rejects a type selector that names no real element, which is almost always a class selector that lost its leading dot – valid CSS that silently matches nothing.

tests/test_templatetags.py

Unit tests for the template tags, including the legacy-style auto-detection and its fallbacks.

Admin pages used for coverage

tests/pages.py renders these pages against tests.testapp, whose Widget model and ModelAdmin are built to exercise the widgets the stylesheets target. A rule only counts as live if it matches on at least one of them, so this list is what the coverage check is worth:

index, app_list

The dashboard and the single-app list: module tables, section links and the colMS sidebar layout. A log entry is created first so the “recent actions” list is populated – it is the only place the admin uses .mini.

changelist

Result table, sortable headers, action bar, filter sidebar, search bar, date hierarchy and the paginator. list_per_page is 5 against 12 fixtures, so the list really paginates.

changelist_page2, changelist_search, changelist_filtered

The states the base changelist does not show: a current paginator page, a submitted search, and a selected filter.

add, change

The widest page by far. Between them they render text, slug, textarea, URL, email, integer, decimal, split date/time, date, checkbox, choice select and a read-only UUID field; a foreign key in a related-widget-wrapper; a many-to-many as filter_horizontal; wide, collapse and multi-field (.fieldBox) fieldsets; a fieldset description containing markup (Django renders descriptions with |safe); and both a stacked and a tabular inline.

add_invalid

The same form submitted with errors, for .errorlist and the .flex-container.errors wrapper.

delete, action_confirm

Both delete-confirmation layouts: the single-object page and the delete_selected action interstitial.

view_only_change

The change page as seen by a staff user with view-but-not-change permission. Django renders the submit row’s .closelink only when the form cannot be saved, so this read-only page is the one place that markup appears.

history

The object history table.

popup

An add form with ?_popup=1, for the .popup body class and its submit row.

user_changelist, user_add, user_change

The auth user pages, which the stylesheets target by name via the app-auth and model-user body classes and the password field.

password_change

The admin password change form.

with_message

A successful submission followed through the redirect, so .messagelist markup is present.

login

The logged-out login form.

When a coverage test fails

A reported rule is dead on the Django version being tested. Either the admin changed and the rule needs updating, or the rule is obsolete and should be deleted. If neither applies, the rule belongs in one of three lists in tests/test_selector_coverage.py, all of which carry a reason per entry:

NOT_SERVER_RENDERED

Markup this suite can never see, because a script builds it in the browser (.selector from SelectFilter2.js, the .datetimeshortcuts icons) or another package ships it (django CMS, django-parler, django-select2). A browser-driven visual regression suite would cover these; this one says so rather than pretending.

VERSION_GATED

Rules for markup a newer Django introduced, correctly dead below it. The boundaries are established by running the suite against each release, not guessed.

KNOWN_STALE

Pre-existing dead rules, pinned so the suite starts green. Each entry is a to-do, not an excuse.

The first two lists are the interesting ones to keep short. Entries are checked against the stylesheets, so a rule that is later deleted cannot linger in a list.

To add a page to the sample, add it to render_all() in tests/pages.py; adding a widget type usually means a field on tests/testapp/models.py and its ModelAdmin.