Expected Behavior

const sym = Symbol('foo');
expect({}).toEqual({[sym]: 'foo'});

This test should fail. It currently passes.

Current Behavior

Is there any guide on writing a launcher? Looking over the current implementations there didn't seem to be much consistency. Looking for best practices.

Pre-check

• [x ] I'm aware that I can edit the docs and submit a pull request

Describe the improvement

I'd like to report

• Unclear documentation
• A typo
• Missing documentation
• Other

Description of the improvement / report
Auto Completion page suggests ho

I can obtain record list (in JSON) from server.
jsonTypes handler passes if record list is filled with designated items.
However jsonTypes handler seems to disallow empty record list: Expected '*' not found (path 'records.*')

repro/test.js:

const frisby = require('frisby'),
  Joi = frisby.Joi;

it('should pass', (done) => {
  frisby.fromJSON({ records: [] })
    .inspectBody()

/** @jsx React.createElement */ doesn't apply to babel-plugin-transform-react-jsx. I assume that the regex expression has some issue to parse 'React.createElement' pragma string.

As a result, 'h' is always [enabled, default](https://github.com/developit/karmatic/blob/5eb2c64c0600e70b86900

Configuration doesn't work in PhpStorm.

My question on StackOverflow https://stackoverflow.com/questions/60521964/how-to-configure-jest-in-phpstorm-for-react-application-create-react-app-flavor

Duplicate it here.
When I specify jest config in a separate file, jest-environment-enzyme can't parse or see it or anything.
But it can see config if I specify it in package.json, but anyway it thro

Issue description or question

The coverage markers usually remain green for the lines that contain the test declaration in Jest. This is usually not a problem until those tests are collapsed (folded). When the tests are folded, then it becomes more difficult to tell that the tests did not run just by scanning the coverage markers.

For example:

![image](https://user-images.githubuserc

Just noticed it is out of date and should match or even just link to https://github.com/JamieMason/Jasmine-Matchers/tree/master/examples/jest

In chapter 1, the quiz question number 4:

You must include react-com.js in order to render React elements on a web page.

The answer to this is true. I believe it should be true for react-dom.js instead of react-com.js.

Preset Pattern:
1.Application Type -> 2.Bundler -> 3.Test Framework -> 4.Publishing -> 5.CI -> 6.CD

create-ts-lib --preset default  my-package
create-ts-lib --preset minimal my-package

Where

• default
  1.Typescript, 2.Webpack, 3.Karma+Jasmine, 4.Semantic Release, 5.CircleCI
• minimal
  1.Typescript, 2.None, 3.None, 4.None, 5.None

Or

create

Problem description:

plugin and pluginName are plugin-centric.
I would like to test a preset which bundle a couple of plugins.

Suggested solution:

Could you please document how to do that (if it's possible)?

The current documentation lacks information on dependency injection and best practices for doing so. Also, it misses to point out that only constructor level injection is being supported and it also misses to point out why, at the test method level or lifecycle hook level, no injection can take place.

It also misses information on the available DI containers, and why one should not make the tes

Let's standardize on what Jasmine does: describe declares a "suite" and it declares a "spec".

This will make it less confusing for future users and contributors, and is especially important for ExampleSpec since that is what people see first when they find Spectrum on GitHub.

To do:

• Read/seach through Spectrum's tests to find usages and mis-usages of "suite", "spec", and "test"
• [