Fredrik Teschke
@ftes.de
96 followers 180 following 120 posts
Elixir full-stack developer with that extra boost 🚀
Posts Media Videos Starter Packs
ftes.de
Any hints on how to implement resource sharing in ExUnit tests?

For phoenix_test_playwright, I want shared browser instances.
Browser pool, each test module has to wait for available browser in `setup_all`.
github.com/ftes/phoenix...

Have you seen/implemented something similar before?
#elixirlang
Feature request: Limit number of concurrent e2e tests · Issue #75 · ftes/phoenix_test_playwright
Hello 👋 Big thank you for your library, it made it possible to easily test my live_vue project. Just one small question: I enjoy running all my tests with mix test, no matter if they're e2e or not....
github.com
ftes.de
What happened that led to drastic drop of hex.pm downloads roughly 2 weeks ago?
#elixirlang
ftes.de
"Let it Crash - Designing Robust Systems"
Our talk included a Live Demo with audience participation.

👇 More details about what Marcus and I did at Dev Connect OWL.
ftes.de/articles/202...
#elixirlang
Complecting code paths: Meme with 3 spidermen pointing at each other.
ftes.de
How do you find a misbehaving part of your software?

Patience 🤣
Monitoring & Metrics (Prometheus, Grafana, cAdvisor, PRTG)
Error Tracking & Logging (Sentry, Firebase, log files)
Observability & Tracing (OpenTelemetry, metrics, distributed tracing)
User Feedback
ftes.de
What are your building blocks for robust systems?

Testing & Monitoring (unit/load tests, monitor, health checks)
Fault Tolerance (redundancy, circuit breakers, loose coupling)
Simple Architecture (KISS)
Load Distribution (client-side calcs)
"I would ask you" 🤣
ftes.de
We asked two questions at our talk "Let it Crash - Designing Robust Systems".

What are your building blocks for robust systems?
How do you find a misbehaving part of your software?

Great answers in thread👇
My takeaway: The BEAM provides. Little need for other tools.
#elixirlang #devconnectowl
ftes.de
PhoenixTestPlaywright 0.8 released 🎉

- ⚡️ speed up refute_has
- ✅ support bunx
- ✅ support phoenix_test 0.8

And other quality of dev-life improvements.

#elixirlang
PhoenixTestPlaywright 0.8 changelog
Reposted by Fredrik Teschke
sasajuric.bsky.social
Sharing this with a big recommendation. You'll have a hard time finding someone as knowledgeable as @hauleth.dev
hauleth.dev
Hi Bsky hivemind, is anyone looking for seasoned #ElixirLang developer? EMEA-based, fully remote.

Either consulting or full-time.
ftes.de
Not trying to blow my own horn here.
Probably mostly symptomatic of playwright being a fairly large project with multiple clients -> stable internal API, even if undocumented.
ftes.de
phoenix_test_playwright user base has grown to 50% of phoenix_test (judging by number of downloads in past 7 days).
Surprises:
1. High number of users. Metric skewed by few power users?
2. Low support effort. Lib is 90% undocumented playwright internals. Playwright js frequently updated.
#elixirlang
ftes.de
🤯
git commit --fixup
git rebase -i --autosquash
ftes.de
Local code review = more collaboration (everybody edits/shares/reviews)
This really resonates with me, I have often wished for that.

youtu.be/MUqvXHEjmus?...
Coding is more collaborative via Jane Street local code review approach
ftes.de
Interesting. With which of the 4 points would it help? Have you used it before?

Looks like WIP and - like igniter - aimed at transforming code. Unsure how that would help?!
ftes.de
Unit testing:
In test, import extracted hook from manifest file, just like you do in your `app.js`. Remember to run `mix compile` first so that the hooks are extracted into `_build`
Depending on your test setup, you may have to alter `NODE_PATH` just like you do for esbuild.
ftes.de
Formatting:
No support by LiveView.HTMLFormatter.
Can we expect built in formatting or extension points for external JS formatting tools in future? I don't know.
ftes.de
JS Intellisense (language server features):
Same as for 'Code highlighting'.
ftes.de
Code highlighting:
Same support as normal `<script>` tags.
Currently for zed: No highlighting in `.html.heex` files or `~H` sigils.
ftes.de
LiveView colocated hooks:
Skip for now due to lack of tooling support?

1. Code highlighting
2. JS Intellisense (language server features)
3. Formatting
4. Unit testing

Any thoughts?
Some of mine in thread 👇

#elixirlang
ftes.de
Unit testing:
In test, import extracted hook from manifest file, just like you do in your `app.js`. Remember to run `mix compile` first so that the hooks are extracted into `_build`
Depending on your test setup, you may have to alter `NODE_PATH` just like you do for esbuild.
ftes.de
Formatting:
No support by LiveView.HTMLFormatter.
Can we expect built in formatting or extension points for external JS formatting tools in future? I don't know.
ftes.de
JS Intellisense (language server features):
Same as for 'Code highlighting'.