mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-12-23 09:52:26 +01:00
f47cfbbb3e
The `assert` module has two modes: "Legacy" and "strict". When using strict mode, the "strict" version of each assertion method is implied. Whereas in legacy mode, by default it will use the deprecated, "loose" version of each assertion. We now use strict mode everywhere. A few tests required updates where they were asserting the wrong thing, and it was passing beforehand due to the loose matching.
71 lines
1.6 KiB
JavaScript
71 lines
1.6 KiB
JavaScript
import { strict as assert } from 'assert';
|
|
import migration31 from './031';
|
|
|
|
describe('migration #31', function () {
|
|
it('should set completedOnboarding to true if vault exists', function (done) {
|
|
const oldStorage = {
|
|
meta: {},
|
|
data: {
|
|
PreferencesController: {
|
|
tokens: [
|
|
{ address: '0xa', symbol: 'A', decimals: 4 },
|
|
{ address: '0xb', symbol: 'B', decimals: 4 },
|
|
],
|
|
identities: {
|
|
'0x6d14': {},
|
|
'0x3695': {},
|
|
},
|
|
},
|
|
KeyringController: {
|
|
vault: {
|
|
data: 'test0',
|
|
iv: 'test1',
|
|
salt: 'test2',
|
|
},
|
|
},
|
|
},
|
|
};
|
|
|
|
migration31
|
|
.migrate(oldStorage)
|
|
.then((newStorage) => {
|
|
assert.equal(
|
|
newStorage.data.PreferencesController.completedOnboarding,
|
|
true,
|
|
);
|
|
done();
|
|
})
|
|
.catch(done);
|
|
});
|
|
|
|
it('should set completedOnboarding to false if vault does not exist', function (done) {
|
|
const oldStorage = {
|
|
meta: {},
|
|
data: {
|
|
PreferencesController: {
|
|
tokens: [
|
|
{ address: '0xa', symbol: 'A', decimals: 4 },
|
|
{ address: '0xb', symbol: 'B', decimals: 4 },
|
|
],
|
|
identities: {
|
|
'0x6d14': {},
|
|
'0x3695': {},
|
|
},
|
|
},
|
|
KeyringController: {},
|
|
},
|
|
};
|
|
|
|
migration31
|
|
.migrate(oldStorage)
|
|
.then((newStorage) => {
|
|
assert.equal(
|
|
newStorage.data.PreferencesController.completedOnboarding,
|
|
false,
|
|
);
|
|
done();
|
|
})
|
|
.catch(done);
|
|
});
|
|
});
|