Meet Ember 3.17 🆕, tell us about your EmberConf experience ❤️, read about testing best practices on the Ember Testing Guide 📗, comment on the co-located test RFC ⛓, embrace easier release management for your apps 📦🙌, learn how to add CI with GitHub Actions ✅, and respect the underscore 🙇.
Last, but not least, we have one request for those of you who attended EmberConf 2020:
Tell us about someone new that you got to chat with at the virtual conf!
Let us know about your answer to this question either by tweeting us via Twitter using the hashtag #EmberConFriends or as a message on the Ember Discord in the #support-ember-times channel. We will raffle an exclusive EmberConf retro sticker set among all story writers by April 6, 2020. We're looking forward to hear from you and happy catching up on virtual EmberConf!
Dawid Pośliński (@PoslinskiNet) wrote about testing best practices and which addons to use in the newly released Ember Testing Guide v1. The testing guide goes through why we need tests to begin with. What benefits does testing give us and what gaps are still present.
Following that, the testing guide discusses best practices in how we architect our testing code. It also goes through how to use the right kind of test. Should the test be unit, integration, acceptance, visual regression, or even manual? These principles are the building blocks to constructing effective tests.
Another, recent RFC wants to take the principle of co-location even a step further: it proposes that test files, e.g. those for rendering tests of a component, should be co-located right next to the respective component class and template files. Beyond that, the proposal suggests a similar co-location pattern for unit tests of related routes and controllers, too - with the motivation to improve the discoverability of tests for application developers.
Ready to learn more about how this could be implemented? Be sure to read the full proposal and to leave your thoughts or questions in the comments below!
Who doesn't dream of easy-peasy releases? Let straightforward publishing workflows become your new reality with create-rwjblue-release-it-setup. Leveraging the tools from the popular library release-it, it allows you to setup your project swiftly for automated versioning and package publishing.
Make your dream of easier release management come true with one single npm command:
npm init rwjblue-release-it-setup
...or a yarn command for that matter:
yarn create rwjblue-release-it-setup
Check out the v2 release page to learn more about all the latest features and improvements and happy publishing!
Continuous integration (CI) and continuous deployment may be skills that you get to practice maybe once on a production app, depending on your job title. But the truth is, you can practice them (ahem) continuously at an early stage for any app, no matter who you are. 💗
You might then ask, where can I learn how to add CI to my Ember app? Are there cool things that I can do because I have an Ember app?
In his blog post, Isaac Lee (@ijlee2) shows step-by-step how you can write a GitHub Actions workflow. Thanks to Ember's addon ecosystem, you can:
Cache dependencies (avoid yarn/npm install)
Lint files and dependencies
Run tests separately from linting
Split tests and run in parallel
Take Percy snapshots in parallel
If you wanted to solve these problems or needed a reference code, look no further! Feedback is always welcome (you can DM @ijlee2 on Discord).