Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This came out of: #19878
The motivation being that I felt it's kinda difficult to quickly throw a reproduction / failing test PR together, because of the custom test harness used so far. I'm in agreement that the existing test stuff should be used first for performance reasons, but I think the utility and integration of a full app is useful for a starting point and easing initial contribution from people. 🎉
Update: (why I think this kind of test is useful)
even after trying to re-create this test,
using only internal testing tools:
I'm at a loss (at the time of writing) -- reproducing whatever the behavior is available to apps is very difficult (to me anyway). I could be that I'm just thick, and I don't know what I'm doing (likely! lol), but I'd like to help lower the barrier to entry for writing tests for ember, ya know?