logger.test.js is a bit of a mess

[jongpie]

One possibility that might help to clean things up in that test class such that you don't need to repeat yourself so much would be using parameterized tests:

const getMarkupLogger = async () => {
  const logger = createElement('c-logger', { is: Logger });
  document.body.appendChild(logger);
  await flushPromises();
  return logger;
};

// and then in a describe block
  it.each([[createLogger], [getLogger], [getMarkupLogger]])('returns user settings', async loggingFunction => {
    getSettings.mockResolvedValue({ ...MOCK_GET_SETTINGS });
    const logger = await loggingFunction();

    const userSettings = logger.getUserSettings();

    expect(userSettings.defaultSaveMethod).toEqual('EVENT_BUS');
    expect(userSettings.isEnabled).toEqual(true);
    expect(userSettings.isConsoleLoggingEnabled).toEqual(false);
    expect(userSettings.isLightningLoggerEnabled).toEqual(false);
  });

In this example, each inner list passed to .each can have any number of arguments that are then passed to the second function, a la:

 it.each([
    [createLogger, 'createLogger'],
    [getLogger, 'getLogger deprecated'],
    [getMarkupLogger, 'markup logger']
  ])('returns user settings', async (loggingFunction, text) => {
 // ...
})

What do you think? I will continue reviewing, but that might really help to cut down on the duplication in that file

Originally posted by @jamessimone in #775 (comment)

Follow-up comment posted by @jongpie in #775 (comment)