Add v3 API to README.

[rwjblue]

The new setupTest / setupRenderingTest API's need to be documented in the README. The existing moduleFor* API's should continue to be listed, but be less prominent.

[jacobq]

Is this mainly the switch to using promises? #292 I'm still early in the learning process of Ember app testing but would be willing to give this a shot.

[acorncom]

@jacobq The new testing approach is documented on guides at this point (currently at https://guides.emberjs.com/v2.18.0/testing/acceptance/ but once I'm finished with a deploy here, 2.18 won't have it documented but https://guides.emberjs.com/v3.0.0/testing/acceptance/ will)

[jacobq]

@acorncom OK, I was wondering about that. I'll keep working my way through the guide pages on testing and will plan to start a PR with the readme changes here after the 3.0 guides are up.

[acorncom]

@jacobq K, 3.0 release is up, would love to hear if you hit any snags on the latest testing info there 😀

[jacobq]

@acorncom Could you help me understand what start-app.js does?
The guides mention that you need to add your custom helpers to it when writing tests for an application, but this file doesn't appear to exist in new addons, and I'm wondering how to bring-in custom helpers there. (In particular, I am trying to update ember-sortable to use ember-cli 3.0 and the new testing conventions.)

It looks to me like RFC268 says start-app.js isn't needed / used anymore. There are also some references to this in the ember-cli guide.

[acorncom]

@jacobq I believe your reading of that RFC is accurate. When I check the latest app blueprints, it looks like we now use tests/test-helper.js which would be where any global helpers might be registered. But I'm not positive on that. Might be worth opening a PR where your writeup can be critiqued ...

[Turbo87]

it looks like we now use tests/test-helper.js which would be where any global helpers might be registered.

there should not be any "global helpers" anymore. if you require any helper functions you should explicitly import them instead of using the registerAsyncHelper() functions.

[jacobq]

@Turbo87, OK, but then why does ember g test-helper some-helper generate (e-cli 3.1.0-beta.1) generate the code below? Do the blueprints and guide need to be updated to reflect this?

import { registerAsyncHelper } from '@ember/test';

export default registerAsyncHelper('someHelper', function(app) {

});

[Turbo87]

because there is no such thing as a "test-helper" anymore and that blueprint should be deleted IMHO

[rwjblue]

Fixed by #320