Using jest and enzyme with next-multilingual

How to enable this component for writing tests of app?

When using e.g. next-translate we made following test:

jest.config.js

import Enzyme from 'enzyme';
import Adapter from '@wojtekmaj/enzyme-adapter-react-17';
import i18n_config from './i18n';

// enable next-translate for testing
global.i18nConfig = i18n_config;

// append the react enzyme adapter
Enzyme.configure({ adapter: new Adapter() });

test/examples/localeTest.js

import getT from 'next-translate/getT';

describe('Next translate', () => {
  it('should match the translated string', async () => {
    const t_en = await getT('en', 'common');
    const t_de = await getT('de', 'common');
    const text_en = t_en('Welcome');
    const text_de = t_de('Welcome');
    expect(text_en).toBe('Welcome');
    expect(text_de).toBe('Willkommen');
  });
});

---

Is there something similar to enable testing for own components with next-multilingual?

Thanks for your help in advance.

[TomFreudenberg]

Ok, I got the issue.

while working on my fork I had not set the fileExtension to load. Therefor the files could not be located.

But when using your original it is missing wile the babel on jest is running BEFORE initialization of new Config. Therefore applicationId is not set.

I solved that on my fork due to params opts from .babelrc

[nbouvrette]

Yes, during compilation, the Babel plugin will inject the messages from all properties files associated with the file, based on naming conventions.