I used the new Ember QUnit theme on a project and it's so great! https://buff.ly/3MOIbBY Ember's testing fundamentals are really strong, and I'm excited to see work to polish surface level details. They make a big difference.
If you're intrigued, try it out. You just might have some fun! There's still work to do to make the Polaris experience smooth out of the box for everyone. If it sounds interesting, please help! Together, we can build a better future for everyone.
The talk dug into two examples: - the surprising benefits of Ember's test suite running in a real browser environment - the way Ember's new component format combines the clarity of Single File Components with the smooth JS interop of JSX. Check it out!
The TL;DR is: Sometimes Ember's differences are what make it so great to use Ember.
If you want to see the speaker notes, emberfest-2024-keyno... But I wrote them for myself (for a presentation that I gave at 3am Pacific Time this morning) so I can't promise that they're totally comprehensible.
My EmberFest opening keynote slides are up! If you've been following my blog posts lately, you'll find that there's a lot in common. emberfest-2024-keyno...
I get into more details in the post and answer some common questions about this approach in detail. Check it out! And as always, have fun! Together, we can build a better front-end future for all of us.
And apps use the same ember-try infrastructure to run their test suites against beta or canary builds to identify potential breakage ahead of time.
And the standard ember-try addon makes it easy for addons to test against their Ember support matrix. Addon tests are written inside of a normal Ember app, so they're running in an environment that most closely resembles the environment in which they will run.