Files
python-tdd/src/functional_tests/test_jasmine.py

24 lines
1016 B
Python
Raw Normal View History

bud panels duplicate-add guard: server-side already_present flag + client-side error Brief w. FYI flash highlight on the existing entry — for each of the three #id_bud_btn panels (My Buds / post-share / gatekeeper-invite), the JSON response from add_bud / share_post / invite_gamer now carries `{already_present, recipient_display, recipient_user_id}`; bud-btn.js branches on `already_present` → calls new Brief.showDuplicateBanner({display_name, target_selector}) instead of the normal onSuccess append; banner title reads `@<username> is already present`, NVM dismisses, FYI dismisses AND eases in the `.bud-duplicate-flash` class (`color: var(--terUser); text-shadow: 0 0 .5em var(--ninUser); transition: 600ms`) onto the existing element (`.bud-entry .bud-name` / `.post-recipient[data-user-id=…]` / `.gate-slot.filled[data-user-id=…]`); gatekeeper "already present" = recipient is either GateSlot.FILLED + gamer OR has TableSeat OR has a pending RoomInvite (highlight target only set when seated — pending invites have no visible slot); .post-recipient chips + .gate-slot.filled cells gain data-user-id so the FYI selector can find them; my_buds.html now loads note.js via the {% block scripts %} pattern (Brief module is required by the duplicate banner path); bonus: latent test_jasmine.py bug fixed — `"0 failures" in result.text` matched "10 failures" / "20 failures" / etc, silently passing up to 99 failed specs; replaced w. `re.search(r"(?<!\d)0 failures\b", …)` (caught my new red specs, would've caught any prior Jasmine regression); 18 new ITs + 10 new Jasmine specs + 3 new FTs (one per panel) — TDD Code architected by Disco DeDisco <discodedisco@outlook.com> Git commit message Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 16:40:15 -04:00
import re
from selenium.webdriver.common.by import By
from .base import FunctionalTest
class JasmineTest(FunctionalTest):
def test_jasmine_specs_pass(self):
self.browser.get(self.live_server_url + "/static/tests/SpecRunner.html")
def check_results():
result = self.browser.find_element(By.CSS_SELECTOR, ".jasmine-overall-result")
bud panels duplicate-add guard: server-side already_present flag + client-side error Brief w. FYI flash highlight on the existing entry — for each of the three #id_bud_btn panels (My Buds / post-share / gatekeeper-invite), the JSON response from add_bud / share_post / invite_gamer now carries `{already_present, recipient_display, recipient_user_id}`; bud-btn.js branches on `already_present` → calls new Brief.showDuplicateBanner({display_name, target_selector}) instead of the normal onSuccess append; banner title reads `@<username> is already present`, NVM dismisses, FYI dismisses AND eases in the `.bud-duplicate-flash` class (`color: var(--terUser); text-shadow: 0 0 .5em var(--ninUser); transition: 600ms`) onto the existing element (`.bud-entry .bud-name` / `.post-recipient[data-user-id=…]` / `.gate-slot.filled[data-user-id=…]`); gatekeeper "already present" = recipient is either GateSlot.FILLED + gamer OR has TableSeat OR has a pending RoomInvite (highlight target only set when seated — pending invites have no visible slot); .post-recipient chips + .gate-slot.filled cells gain data-user-id so the FYI selector can find them; my_buds.html now loads note.js via the {% block scripts %} pattern (Brief module is required by the duplicate banner path); bonus: latent test_jasmine.py bug fixed — `"0 failures" in result.text` matched "10 failures" / "20 failures" / etc, silently passing up to 99 failed specs; replaced w. `re.search(r"(?<!\d)0 failures\b", …)` (caught my new red specs, would've caught any prior Jasmine regression); 18 new ITs + 10 new Jasmine specs + 3 new FTs (one per panel) — TDD Code architected by Disco DeDisco <discodedisco@outlook.com> Git commit message Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 16:40:15 -04:00
# Word-boundary anchor — Jasmine 6 reports as "N specs, X failures".
# Plain `"0 failures" in text` matches "10 failures", "20 failures",
# etc., letting up to 99 failed specs slip past as green.
if not re.search(r"(?<!\d)0 failures\b", result.text):
failures = self.browser.find_elements(
By.CSS_SELECTOR, ".jasmine-failed .jasmine-description"
)
detail = "\n".join(f.text for f in failures) if failures else "(no detail)"
self.fail(f"{result.text}\nFailing specs:\n{detail}")
self.wait_for(check_results)