test(docker): a plugin template can take its own name; the overview's assertions follow its new tables (#5299, #5302)

render_plugin_template's first three arguments are positional-only, so the
service page's own `name` reaches the template. The overview names a service
rather than its replica containers, and a stack chip keeps the search it was
clicked under.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-07 20:11:46 -04:00
co-authored by Claude Opus 5.5
parent 2093f399e6
commit a775882bd4
3 changed files with 8 additions and 4 deletions
@@ -136,6 +136,7 @@ def test_a_service_page_reads_every_task(app):
rows = got["rows"][1]
assert f'href="/plugins/docker/service/{name}"' in rows
assert f'<a class="chip" href="/plugins/docker/?stack=it{tag}"' in rows
# A stack chip keeps the search it was clicked under.
assert f'<a class="chip" href="/plugins/docker/?q=it{tag}&amp;stack=it{tag}"' in rows
assert f'/plugins/docker/service/{name}?task={dead_task}#logs' in rows # the failure's logs
assert f'href="/plugins/docker/service/{name}"' not in got["other"][1]