Skip to content

feat: Run tests for sub packages in CI #374

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

Merged
merged 13 commits into from
Dec 20, 2019

Conversation

zashraf1985
Copy link
Contributor

@zashraf1985 zashraf1985 commented Dec 13, 2019

Summary

Travis CI Only run tests for optimizely-sdk package. This PR makes Travis CI run unit tests for other sub packages on node 12

Test Plan

Tested on Travis CI

@coveralls
Copy link

coveralls commented Dec 13, 2019

Coverage Status

Coverage remained the same at 97.537% when pulling c35fd4c on zeeshan/multi-package-unit-tests into 6999786 on master.

@zashraf1985 zashraf1985 force-pushed the zeeshan/multi-package-unit-tests branch from c6c356b to 8b40939 Compare December 13, 2019 11:03
@zashraf1985 zashraf1985 force-pushed the zeeshan/multi-package-unit-tests branch from 8b40939 to 01cfb98 Compare December 13, 2019 12:10
@zashraf1985 zashraf1985 force-pushed the zeeshan/multi-package-unit-tests branch from 5322be5 to 605e08a Compare December 14, 2019 20:08
@zashraf1985 zashraf1985 changed the title feat: Run tests for subpackages in CI feat: Run tests for sub packages in CI Dec 15, 2019
@zashraf1985 zashraf1985 marked this pull request as ready for review December 15, 2019 18:39
@zashraf1985 zashraf1985 requested a review from a team as a code owner December 15, 2019 18:39
@zashraf1985 zashraf1985 requested a review from mjc1283 December 15, 2019 18:40
.travis.yml Outdated
stage: 'Test sub packages'
node_js: '12'
before_install: cd packages/datafile-manager
before_script: tsc
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this tsc necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

not needed. i just checked. looks like jest automatically compiles typescript before use

@@ -62,7 +62,7 @@ export function objectValues<K>(obj: { [key: string]: K }): K[] {
return Object.keys(obj).map(key => obj[key])
}

export function objectEntries<K>(obj: { [key: string]: K }): [string, K][] {
export function objectEntries<K>(obj: { [key: string]: K }): (string | K)[][] {
Copy link
Contributor

Choose a reason for hiding this comment

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

What is this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is fixing a tsc compilation error. return type was not correct.

@zashraf1985 zashraf1985 removed their assignment Dec 16, 2019
@@ -42,6 +42,7 @@
"devDependencies": {
"@types/jest": "^23.3.12",
"jest": "^23.6.0",
"ts-jest": "^23.10.5"
"ts-jest": "^23.10.5",
"typescript": "^3.7.3"
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change typescript dependency versions to "3.3.3333" in all packages

@mjc1283 mjc1283 merged commit bbdb2cc into master Dec 20, 2019
@mjc1283 mjc1283 deleted the zeeshan/multi-package-unit-tests branch December 20, 2019 16:49
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.

4 participants