Does this work with Atom 1.24?

[stevenzeck]

Hi. I've been trying to get this setup on my Atom package. I keep receiving an error when I have this simple test:

describe("My Delightful Package", () => {
  it("knows about all of Atom's loaded packages", () => {
    const packages = atom.packages.getLoadedPackages();
    expect(packages).toMatchSnapshot();
  })
})

ReferenceError: atom is not defined

[keplersj]

I'm afraid to say this is a very troubled, and experimental package at the moment.

If you wouldn't mind could you tell me how you ran the test to help confirm some of my theories? atom --test .? apm test?

[keplersj]

As well, I've updated the README to reflect the recommended configuration to use jest-preset-atom.

[Glavin001]

I think this will not work because Jest runs tests in a separate process and does not pass through global: jestjs/jest#4643
Looks like a custom test environment may be required? See jestjs/jest#4506

@keplersj Did you actually have this working at one point?

[keplersj]

@Glavin001 I did. That's the most infuriating thing. I had it working with a version of crystal-lang-tools/language-crystal.

A custom test environment is being used in jest-preset-atom.

[stevenzeck]

@keplersj if I use that preset it just hangs, opens another Atom instance in the background like it usually does for tests, but just stays like that.

[keplersj]

@szeck87 Are you using the menu item in app, atom --test ., or apm test?

[stevenzeck]

atom --test .

[keplersj]

Able to replicate with version 0.1.3 of jest-preset-atom and version 0.1.3 of atom-test-runner-jest.

[stevenzeck]

Yep, and without that in there it does run, just still doesn't recognize atom.

[keplersj]

I just updated jest-preset-atom so that the environment correctly passes down the Atom global. Does it work with jest-preset-atom@0.1.4 and Jest config set to the following:

{
  "testEnvironment": "jest-preset-atom/environment"
}

[keplersj]

Defining just the testEnvironment like that doesn't do anything to handle non-ES6 transforms, so the test runner will not handle any specs or required files written in CoffeeScript or TypeScript like Atom will by default.

[keplersj]

I just updated jest-preset-atom to version 0.1.5. And the following Jest config is working with crystal-lang-tools/language-crystal locally:

{
  "preset": "jest-preset-atom"
}

[stevenzeck]

Yea I'm getting somewhere. Now getting errors on the waitsForPromise not being defined since I can't use async/await. Thanks!

[keplersj]

waitsForPromise is exclusive to Jasmine. Feel free to async/await in Jest

[keplersj]

I'm gonna close this because we made progress on running. There are other issues. So, please continue to open issues. Thank you so much!