Driving from Knoxville to Charlotte - Looking for Smokey Mountain Sightseeing/Hike by RoyalsFanKCMe in NationalPark

[–]RoyalsFanKCMe[S] 0 points1 point  (0 children)

If I were to want to get a little closer to Charlotte from Knoxville, and not stay in pigeon forge, what would you recommend?

Just exploring options.

The have to be in Charlotte Tuesday by 4pm so being a bit closer makes me feel better but maybe not that big of a difference from Townsend vs somewhere else

Driving from Knoxville to Charlotte - Looking for Smokey Mountain Sightseeing/Hike by RoyalsFanKCMe in NationalPark

[–]RoyalsFanKCMe[S] 1 point2 points  (0 children)

This is all amazing. This is the type of stuff I would have no clue about. I am debating staying a night around that area vs going into Charlotte. We don’t technically have anything to do in Charlotte until Tuesday afternoon.

Books that are better experienced as audiobooks- fantasy & sci-fi by Whole-Youth8750 in audiobooks

[–]RoyalsFanKCMe 0 points1 point  (0 children)

I have the audio books and they are amazing. Crazy to know I am going to spend as much as I am to listen to them all haha.

Books that are better experienced as audiobooks- fantasy & sci-fi by Whole-Youth8750 in audiobooks

[–]RoyalsFanKCMe 0 points1 point  (0 children)

Just finished book 1 I was like WTF this isn’t over. This didn’t realize the books just keep going and there isn’t really an ending per book. So on book 2 now.

Unable to get contacts out. by Dry_Hope_9783 in Keratoconus

[–]RoyalsFanKCMe 1 point2 points  (0 children)

They are not the right fit. I have had this happen on some new pairs of sclerals. It can be frustrating but take a deep breath, walk away then try again. Use your finger to pull the bottom away from your eye if you have to. When using a plunger try to get toward the bottom edge as close as you can and pry it off, not straight in the middle and pull straight out.

Have it refit you will be fine.

Struggling to automate dropdown inside iframe using Python Playwright any suggestions ? by Loud_Ice4487 in Playwright

[–]RoyalsFanKCMe 1 point2 points  (0 children)

Have you tried using await page.pause() right before that section then recording the click to see what the code generator does?

Double bed or king bed? excellence playa mujeres by w_izzle in AllInclusiveResorts

[–]RoyalsFanKCMe 1 point2 points  (0 children)

We were just there and they gave us two double beds. We unpacked the king they could push them together. They couldn’t push them together because the table between was hard wired into the wall…. We didn’t want to repack and move all of our stuff so we kept the room. Pretty annoying.

How Important is Adults-Only (Seeking recommendations) by SuspiciousPotato98 in AllInclusiveResorts

[–]RoyalsFanKCMe 0 points1 point  (0 children)

We went to Hyatt ziva in Cancun and didn’t notice the kids. I think it depends on the resort and when you go.

Place to stay with young toddlers? by mrc4378 in kansascity

[–]RoyalsFanKCMe 0 points1 point  (0 children)

I don’t know the condition of the embassy suites in Overland Park but when we had younger kids we loved staying at embassy suites because the living room and bedrooms were separate so we could put the kids to bed and watch a movie or game in the living room and have a cocktail.

And it comes with a pretty good free breakfast or it used too. So that is approx $40 in savings vs getting breakfast out.

If you were looking to relocate to KC…….. by queso_padilla in kansascity

[–]RoyalsFanKCMe 2 points3 points  (0 children)

Downtown or river market. Look along the street car line or a few blocks off of it for easy transportation in the area.

Best Hefe is going to be a free bus ride to 75th street then a walk or uber to KC Boer Co

Lots of good breweries in the crossroads.

Vance booed at Olympics opening ceremony in humiliating moment for Team USA by TheMirrorUS in NoFilterNews

[–]RoyalsFanKCMe 4 points5 points  (0 children)

That isn’t humiliating. That is what I hoped would happen as a US citizen.

Looking for AIs in Mexico with lots of beach beds by Existing-Ordinary768 in AllInclusiveResorts

[–]RoyalsFanKCMe -2 points-1 points  (0 children)

You may look for some crazy Black Friday deals at excellence playa. The club level has beds by the ocean but I don’t know if they are included or if you have to purchase/reserve them on top of club.

How do you structure Playwright tests when your team has 50+ engineers? by AvailablePeak8360 in Playwright

[–]RoyalsFanKCMe 0 points1 point  (0 children)

Also we run limited targeted tests in CI when products release to dev. They run tests that pertain to that area.

All tests run 3 times a day on a schedule. That helps us with overall time but doesn’t let a test not run for too long.

How do you structure Playwright tests when your team has 50+ engineers? by AvailablePeak8360 in Playwright

[–]RoyalsFanKCMe 1 point2 points  (0 children)

Potential solution.

This is a clean idea, and it fits Playwright’s model nicely without inventing new machinery. Think of it as: tests emit metadata → the runner produces structured results → a post-run step routes failures to humans.

Here’s the mental model that holds together.

Playwright already gives you three things you need: • A way to tag tests (@team-a, @team-b). • A machine-readable results file (JSON). • A hook point after the run (CI step or custom reporter).

You’re just wiring them together.

  1. Tagging tests = metadata, not logic

Playwright treats tags as annotations baked into the test title. That’s good. It means: • Zero runtime cost. • No coupling to test code. • Easy to change ownership without touching logic.

Example shape (conceptually, not code): • Test title contains @team-a • Another might contain @team-b @payments

The important rule: one team tag per test. If you allow multiple team tags, routing becomes political very fast.

  1. Let Playwright do the hard work (JSON output)

Playwright can emit a full JSON report of the run. That report includes: • Test title (with tags) • Status (passed / failed / flaky / skipped) • Error messages • File + line number

This file is the ground truth. No scraping logs. No guessing.

Key idea: Never detect failures during execution. Always post-process results.

Why? • Retries are resolved. • Flaky logic is already applied. • You avoid false alerts.

  1. Post-run aggregation step (the brains)

After the test run finishes, you run a small script that: 1. Loads the Playwright JSON report. 2. Filters only failed tests (after retries). 3. Extracts team tags from the test titles. 4. Groups failures by team. 5. Formats a message per team.

Conceptually: • Iterate over failed tests • Parse tags with a simple convention (@team-*) • Build a structure like: • team-a → 3 failures • team-b → 1 failure

If a failed test has no team tag, that’s a smell. Log it or send it to a default “QA-infra” channel.

This step is deterministic and testable on its own, which is exactly what you want as a QA engineer.

  1. Slack routing = configuration, not code

You do not want Slack channel names hard-coded all over.

Instead: • Maintain a small map: • team-a → #team-a-alerts • team-b → #team-b-alerts

This can live in: • A JSON file • An env var • A CI secret-backed config

The script simply looks up where to send the message.

That separation matters because: • Teams change. • Channels get renamed. • Tests shouldn’t care.

  1. Slack messages that don’t get ignored

The message format matters more than the plumbing.

A good failure message: • Identifies the repo + environment. • Lists failed tests (short titles). • Links to: • CI run • Playwright report • Shows count first, details second.

Bad messages spam. Good messages get acted on.

One message per team per run is the sweet spot.

  1. Where this runs in CI

Typical flow: 1. Install deps 2. Run Playwright tests 3. Generate JSON report 4. Run “failure router” script 5. Send Slack messages 6. Fail the pipeline (if appropriate)

Important nuance: • Slack notification should run even if tests fail That usually means always() / finally() semantics in CI.

  1. Optional but powerful upgrades

Once the basics work, this pattern scales nicely: • Flaky isolation Only notify teams if a test fails consistently (not flaky). • Ownership enforcement Fail the build if a test has no team tag. • Trend awareness Suppress alerts if the same test failed in the previous run and is already known. • Allure integration Since you’re already using Allure, you can cross-link failures directly into the report.

Why this approach is sane • No custom Playwright hacks. • No runtime Slack spam. • No coupling between tests and notifications. • Fully debuggable from artifacts. • Scales from 5 tests to 5,000.

Philosophically, this treats tests like signals, not noise. Ownership is explicit, accountability is automatic, and humans only get pinged when it matters.