jasmine 2

[aaronabramov]

i took #5646 as a base

I removed MetaMatchers and instead ran jest on a specific file in a child process and compared the raw string output. It's not ideal, but much simpler than hacking into jasmine internals to compare the suites :)

cc: @zpao @cpojer

[cpojer]

woah, this is awesome. I'll let the React folks merge this one, though :)

[ghost]

@DmitriiAbramov updated the pull request.

[cpojer]

@zpao @sebmarkbage can you think of a way to reduce the amount of permutation in ReactMultiChildText-test.js? It seems like it's taking 150 seconds because of the amount of work it is doing. Is all of this necessary?

[ghost]

@DmitriiAbramov updated the pull request.

[sophiebits]

It is supposed to take less time. I posted a PR earlier today that fixes a severe perf issue. Still slow after the change but not that slow.

[cpojer]

@spicyj where can I see your change? I can't find it.

[ghost]

@DmitriiAbramov updated the pull request.

[sophiebits]

@cpojer Oops, you're right. I forgot to send it. Thanks. #6770

[ghost]

@DmitriiAbramov updated the pull request.

[gaearon]

@DmitriiAbramov Would you mind rebasing please?

[aaronabramov]

@gaearon sure
yeah. it gets out of sync really quickly :)

[facebook-github-bot]

@DmitriiAbramov updated the pull request.

[zpao]

I think this is probably fine. Hacky but fine :). Should we make this fail if both specs are empty?

[sophiebits]

Note that this only checks the list of tests

  ✓ it preserves the name of the class for use in error messages
  ✓ it throws if no render function is defined
  ✓ it renders a simple stateless component with prop
  ✓ it renders based on state using initial values in this.props
  ✓ it renders based on state using props in the constructor
  ✓ it renders based on context in the constructor
  ✓ it renders only once when setting state in componentWillMount
  ✓ it should throw with non-object in the initial state property
  ✓ it should render with null in the initial state property
  ✓ it setState through an event handler
  ✓ it should not implicitly bind event handlers
  ✓ it renders using forceUpdate even when there is no state
  ✓ it will call all the normal life cycle methods
  ✓ it warns when classic properties are defined on the instance, but does not invoke them.
  ✓ it should warn when misspelling shouldComponentUpdate
  ✓ it should warn when misspelling componentWillReceiveProps
  ✓ it should throw AND warn when trying to access classic APIs
  ✓ it supports this.context passed via getChildContext
  ✓ it supports classic refs
  ✓ it supports drilling through to the DOM using findDOMNode

whereas the old one made sure the number of assertions matched. So this is significantly less strict than before.

[aaronabramov]

@spicyj that is true.
Maybe what we can do is add an afterEach hook that will console.log the number of expects in the test and make output look something like:
✓ it supports classic refs [# of expects: 4]
and compare that.
hacky.. but maybe that'll do :)

[sophiebits]

That sounds good to me, can you do that?

[sophiebits]

I think we can merge after that's fixed.

[ghost]

@DmitriiAbramov updated the pull request.

[aaronabramov]

@spicyj i added a custom setup file that monkeypatches jasmine here https://github.com/facebook/react/pull/6769/files#diff-d14cc01bd4a76abb678ced92d16a0e9cR1

it depends on jestjs/jest#1027 and jestjs/jest#1028
which will hopefully be released tomorrow

This is how failure looks like

it will also fail if any of the outputs are empty.

let me know if it makes sense and i'll rebase it again as soon as we ship the new version of jest

[ghost]

@DmitriiAbramov updated the pull request.

[sophiebits]

I think that seems reasonable. Is there a way we can make the output show a more readable diff? Even if not, this seems good – thanks for doing the work!

[aaronabramov]

@spicyj i'll work on the diff next, but that'll be a part of jest :)

[ghost]

@DmitriiAbramov updated the pull request.

[aaronabramov]

jest 12.1.0 is out
this PR is ready to be merged

[cpojer]

can you make it jest?

[ghost]

@DmitriiAbramov updated the pull request.

[gaearon]

Thanks a ton @DmitriiAbramov! I rebased this in #6872 and merged.

[cpojer]

hell yeah! I think no one is using jasmine1 any more now, we'll make it optional in Jest and not download it by default any more :)

[cpojer]

Also the tests should be 20 % faster or so :)

[gaearon]

Also the tests should be 20 % faster or so :)

Yes, it certainly seemed so to me. Great job!