Skip to content

Releases: kaliber5/ember-cli-yadda

Release 0.7.0

19 Oct 17:45
Compare
Choose a tag to compare

💥 Breaking Change

🚀 Enhancement

Committers: 2

Release 0.6.0

06 Nov 09:26
Compare
Choose a tag to compare

💥 Breaking Change

  • #86 Avoid importing yadda from ember-cli-yadda (@simonihmig)
  • #85 Update dependencies, drop support for node < 10, Ember < 3.16 (@simonihmig)

🚀 Enhancement

🐛 Bug Fix

📝 Documentation

🏠 Internal

Committers: 3

Use ember-auto-import instead of ember-browserify

04 Sep 16:07
d529a8f
Compare
Choose a tag to compare

ember-auto-import is used instead of ember-browserify to import yadda.

💥 This is a breaking change.

To upgrade from 0.4.0:

  1. npm install ember-cli-yadda@0.5.0 --save-dev
  2. npm uninstall ember-browserify
  3. In the application test code, replace every instance of:
    import yadda from '../../helpers/yadda';
    with
    import { yadda } from 'ember-cli-yadda';
  4. Delete tests/helpers/yadda.js
  5. Run tests

Use new Testing API

15 Mar 15:47
aed21db
Compare
Choose a tag to compare

Changes

  1. Uses the new testing API (RFC's 232 & 268) to run the BDD tests (#65).

    • 💥 This is a breaking change. Version 0.4.0 requires your tests to be written according to the new testing API. See the Upgrading section below for more info.
  2. Added ability for custom test setup and teardown (#47). See the Annotations | Customization section of the doc for more info.

  3. Added configuration of Yadda options (#72). See the Yadda Configuration section of the doc for more info.

Upgrading

To upgrade to the latest version of this addon from a previous release < 0.4.0, including refactoring your existing tests to Ember's new testing APIs, follow these steps:

  • Install the latest version of ember-cli-yadda.
  • Run ember g ember-cli-yadda to add the most recent files from the blueprint to your project.
  • Add the appropriate setup annotation to each Feature or Scenario.
  • Refactor your step files to use the new testing APIs:
  • Optional: customize tests/helpers/yadda-annotations.js with any additional setup logic that is needed, see Annotations | Custumization.

Upgrade to ember 3.0.0

08 Mar 17:57
27e7c82
Compare
Choose a tag to compare
  1. Upgraded to use ember 3.0.0. Is backwards compatible with ember 2.x applications.
  2. Fixes bug where an error in an async step was not reported to QUnit causing the test to hang.

Run-time Annotations

22 Feb 20:39
4fe0d5f
Compare
Choose a tag to compare
  1. Added run-time annotations (#52).
    • if upgrading from a previous release, run ember g ember-cli-yadda
    • this will install tests/helpers/yadda-annotations.js
    • customize yadda-annotations.js to fit your needs
  2. Updated readme so build status shows correctly (#57).

Quick fix on the blueprint install

08 Dec 22:31
Compare
Choose a tag to compare
  • #41 Fixes blueprint install

npm, @ignore, seperateSteps

07 Dec 09:41
Compare
Choose a tag to compare

Thanks to @simonihmig, @sfbwalder and @dejavs we have new features and better future proofness.

  • #34 Include yadda from npm instead of bower: because of the way yadda was built and put on bower, it was interfering with the ember test runner by moving to npm, and ember-cli-browserify we no longer have this problem.
  • #37 If you use mocha there's a new option you can enable, which will give you better looking tests and better traceability on asynchronous tests. Do this by changing the call to EmberApp in ember-cli-build.js, like this:
var app = new EmberApp(defaults, {
  'ember-cli-yadda': {
    'separateSteps': true
  }
  // Add options here
});

screen shot 2016-12-06 at 15 10 47

- #38 Add the ability to skip tests by adding the `@ignore` annotation.

small accumulated changes

16 Nov 13:01
Compare
Choose a tag to compare

Version 0.1.0

  • fix context in mocha #23
  • don't hide this with arrow functions in generated example steps #26
  • remove expect calls from test #28
  • import destroyApp from consuming app #31

adding configurable yadda version

11 May 14:54
Compare
Choose a tag to compare

forgot to update the package.json