Recently, I've been working on writing unit tests for Sequelize with a Postgres database and using Jest for testing. While trying to get the following code to work:
test('email field only takes valid emails', () => {
expect.assertions(2);
let user = Users.build({ email: 'notAProperEmail', password: 'abc123' });
return user.validate().catch(err => {
expect(err).toHaveProperty('errors');
expect(err.errors[0].message).toEqual('Validation isEmail on email failed');
});
})
I encountered an error "SequelizeDatabaseError: relation "Users" does not exist" which puzzled me. Also, the expect method seems to be missed as I receive the assertion error: "Expected one assertion to be called but received zero assertion calls."
describe('Password is encrypted', () => {
beforeAll(() => {
Users.create({
email: '<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="780c1d0b0c49381f1519111456fb84888">[email protected]</a>',
password: 'testPassword123'
})
});
test('password is not plain text', () => {
expect.assertions(1);
return Users.findOne({where: { email: '<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="b1c5d4c2c580f1d6dcd0d8dd9fd2dedc">[email protected]</a>' }}).then(response => {
expect(2).toEqual(2)
console.log('console log here: ', response);
});
});
I have a hunch that the issue stems from build not saving to the database in time for Jest to make an assertion. Using promises to handle the asynchronous nature seemed like a viable solution according to the Jest documentation. However, even after implementing promises, it still throws an error suggesting that the promises are being resolved before Sequelize finishes fetching data from the Postgres Database. Any insights on this challenge would be highly appreciated!