Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using jest projects config to run tests #135

Merged
merged 4 commits into from
Feb 6, 2019
Merged

Conversation

devaradhanm
Copy link
Contributor

No description provided.

@devaradhanm devaradhanm requested a review from a team January 28, 2019 18:06
@devaradhanm devaradhanm changed the title Using jest projects condig to run tests Using jest projects config to run tests Jan 28, 2019
package.json Show resolved Hide resolved
@dbjorge
Copy link
Contributor

dbjorge commented Jan 28, 2019

The longer I consider the package-lock.json trickery to workaround that jest issue, the less comfortable I am with it - it's just too easy for someone to accidentally revert the workaround. Can you link the Jest issue in question? If we think they're likely to fix it soonish in a patch release, I kind of lean towards waiting for that before merging this.

jestjs/jest#6865

updating deprecated property

remove tsconfig.jest.json

ignore d.ts files form coverage

This reverts commit 7875345cadaee70b4f2cb2c2d5d3d8554fe0354f.
@@ -51,7 +51,7 @@ async function verifyExtensionIsBuilt(extensionPath: string): Promise<void> {

async function launchNewBrowser(): Promise<Puppeteer.Browser> {
// only unpacked extension paths are supported
const extensionPath = `${process.cwd()}/drop/dev/extension/`;
const extensionPath = `${(global as any).rootDir}/drop/dev/extension/`;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i had to make this change to support running "jest" from any directory

});

function verifySnapshot(props: ReportCheckListProps): void {
expect(shallow(<ReportCheckList {...props} />).getElement()).toMatchSnapshot();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

after jest update, shallow matching snapshot, doesnt output anything. So, i had to use getElement

src/tests/jest.common.config.js Outdated Show resolved Hide resolved
Copy link
Contributor

@dbjorge dbjorge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One more readme update

README.md Outdated Show resolved Hide resolved
@devaradhanm devaradhanm merged commit 0e24d72 into master Feb 6, 2019
@devaradhanm devaradhanm deleted the users/devaradhanm/test branch February 6, 2019 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants