allure-mocha - TypeError: Cannot read property 'epic' of undefined

I’m trying to do this configuration, but allure is undefined. Do you have any example calling allure method from mocha tests using TypeScript?

    "allure-mocha": "2.0.0-beta.6",

// es-modules
import { allure } from 'allure-mocha/runtime';
// or commonjs
const { allure } = require('allure-mocha/runtime');

it('is a test', () => {
  allure.epic('Some info');
});

TypeError: Cannot read property 'epic' of undefined

Thank you

[sskorol]

Should work as soon as #138 is merged and a new version is released. I’ve added epic tests and tested it locally with decorators as well. So stay tuned.

[sskorol]

@fescobar @tims-j is there any reason you can’t use es6 import syntax?

The problem here is in a combination of Mocha specifics and plain-old JS require syntax.

First of all, we have to use default export for reporter itself to be able to include it via -R option. On the other hand, we can’t make allure default as well, as allure-runtime makes 3 exports.

So what’s wrong with require syntax then? Nothing special, except the fact that when you destructure allure via require, it detaches it from the reporter context.

The problem here is that this variable’s value is populated in runtime, when AllureReport is initialized by Mocha. So when you detached it via require you couldn’t track any changes anymore. That’s why you got epic of undefined error. However, it would fail the same way for any other property as well.

You may wonder how to fix that? Either use es6 import syntax, which correctly handles destructuring without detaching object from its parent context, or operate with a root runtime object. But in the latter case you can access allure only within test.

import { allure } from "allure-mocha/runtime";

it('is a test', () => {
    allure.epic('Some info');
});

// or
const runtime = require('allure-mocha/runtime')

it('is a test', () => {
    runtime.allure.epic('Some info');
});