We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Assertion Failed: Cannot create a new tag for <(unknown):ember922> after it has been destroyed.
<(unknown):ember922>
test:
import { module, test } from 'qunit'; import { setupTest } from 'ember-qunit'; import StorageObject from 'ember-local-storage/local/object'; import resetStorages from 'ember-local-storage/test-support/reset-storage'; module('Unit | Services | UserOptionsDestroyer', function (hooks) { setupTest(hooks); module('upon a successful user options object destruction', function (hooks) { hooks.beforeEach(function () { const mockStorage = StorageObject.extend(); mockStorage.reopenClass({ initialState() { return { userId: '1', }; }, }); this.owner.register('storage:userOptions', mockStorage); }); hooks.afterEach(function () { window.localStorage.clear(); resetStorages(); }); test('should return a positive response', async function (assert) { assert.expect(1); const service = this.owner.lookup('service:destroyers/user-options-destroyer'); const response = await service.destroyOptions(); const expectedServiceResponse = { success: true, result: null }; assert.deepEqual(response, expectedServiceResponse); }); }); });
Related to #377
The text was updated successfully, but these errors were encountered:
@hexadecy thanks for reporting. I'll try to add tests to cover that and to figure out what is going wrong.
Sorry, something went wrong.
I'm hitting the same issue.
I just noticed that the readme still mentions ember-mocha.
No branches or pull requests
Error: Assertion Failed: Cannot create a new tag for
<(unknown):ember922>
after it has been destroyed.test:
Related to #377
The text was updated successfully, but these errors were encountered: