Legacy runtime API for Allure Mocha

[delatrie]

Context

The legacy API makes Allure Mocha compatible with the code written against pre-3.0 allure-mocha/runtime. The references are Allure.ts and MochaAllure.ts.

Issues:

• No logStep in the new Runtime API (not a big deal, since the legacy logStep can be implemented in terms of step; logStep in 2.15.1 doesn't support custom statuses anyway, so we don't break it).
• The legacy attachment's 3rd argument can be an instance of AttachmentOptions. The new API doesn't allow that. While AttachmentOptions.contentType could be provided directly, there is no way to pass AttachmentOptions.fileExtension.

TODO:

• test testAttachment
• test step's return value

Extra changes

Reporter's new name

The reporter class's name now is AllureMochaReporter (following a general convention Allure<Framework><ExtensionMechanism>.

CommonJS export change for AllureMochaReporter

The CommonJS build of Allure Mocha now exports the reporter class directly as module.exports. That allows users to specify the reporter via CLI: npx mocha --reporter allure-mocha .... That also makes the new version more look-alike with the previous one.

More comprehensive testing of Allure Mocha

The test runner now allows to test running Mocha from code (both CommonJS and ESM). The behavior can be controlled with ALLURE_MOCHA_TEST_RUNNER env var, which supports the following values: cli, cjs, and esm.

ALLURE_MOCHA_TEST_SPEC_FORMAT allows choosing between CommonJS (cjs) and ESM (esm) testing samples.

ALLURE_MOCHA_TEST_PARALLEL allows testing the parallel mode of Mocha.

Currently, only the following two combinations are tested in the CI:

• Runner: cli, specs: esm, parallel: no
• Runner: cli, specs: esm, parallel: yes

ESLint config changes

All files inside dist folders are now ignored by ESLint.

Checklist

• Sign Allure CLA
• Provide unit tests