Skip to content

Added Windows Tests #40

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 12 commits into from
Aug 8, 2020
Merged

Added Windows Tests #40

merged 12 commits into from
Aug 8, 2020

Conversation

TatianaKapos
Copy link
Contributor

@TatianaKapos TatianaKapos commented Jul 31, 2020

Summary

Added Windows tests to ProgressView

  • Since circleCI has issues with windows, used Github actions to create the windows tests.
  • Test simply makes sure each progressbar can be found, will time out and fail if the progressbar does not render and will tell you the specific progress bar it failed at.

image

Checklist

  • I have tested this on a device and a simulator
  • I added the documentation in README.md
  • I mentioned this change in CHANGELOG.md
  • I updated the typed files (TS and Flow)
  • I added a sample use of the API in the example project (example/App.js)

.eslintignore Outdated
jest-setups/jest.setup.js
jest-setups/jest.setup.windows.js
__tests__/ProgressViewWindows.test.js
Copy link

Choose a reason for hiding this comment

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

is it necessary to ignore this file?

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 removed the test file from this file but both jest-setup files gives me a 'platform' is not defined no-undef error even though it's defined in the setup.windows

Comment on lines 46 to 57
- name: NuGet restore
run: nuget restore example\windows\ProgressViewExample.sln

- name: Build x64 release
run: msbuild .\example\windows\ProgressViewExample.sln /p:Configuration=Release /p:Platform=x64 -m

- name: Deploy
shell: powershell
run: |
cd example
Copy-Item -Path windows\x64\Release -Recurse -Destination windows\
npx react-native run-windows --arch x64 --release --no-build --no-packager
Copy link

Choose a reason for hiding this comment

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

sorry let me rephrase: can we just replace all of this with just running yarn windows or npx react-native run-windows?

Copy link

Choose a reason for hiding this comment

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

I remember seeing some bundling errors when building release using just run-windows command, maybe that's fixed now. @TatianaKapos you can try replacing all this with npx react-native run-windows --arch x64 --release --no-packager and see if it works.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hmmm yeah I'm seeing an error where it can't find the package in the release folder :/

@TatianaKapos TatianaKapos marked this pull request as ready for review August 4, 2020 19:30
@TatianaKapos
Copy link
Contributor Author

@Naturalclar This PR had been reviewed, let me know if you need me to make any changes! :)

Copy link
Member

@Naturalclar Naturalclar left a comment

Choose a reason for hiding this comment

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

@TatianaKapos Thank you <3

@Naturalclar Naturalclar merged commit 5138d19 into react-native-progress-view:master Aug 8, 2020
@chrisglein
Copy link

I was looking to add the Windows state to reactnative.directory, but it appears that we need a new published update that this contains this merged PR. In particular to address the part to fix the package files that was originally a separate PR but then was included in this PR.

The change is in, there just needs to be a new publish to NPM. @Naturalclar are releases being done on demand? What's the criteria for pushing out a new one?

@TatianaKapos Did we get validation that if the windows folder is published then the Windows version is all good?

@Naturalclar
Copy link
Member

@chrisglein I can release the package on demand. I thought the PR only added test and no change to the actual functionality of the code, so I didn't make a release, sorry about that!
I'll make a new release soon

@TatianaKapos
Copy link
Contributor Author

My bad, should have specified the fix in the PR! But I just checked and it fixes the windows issue.

@asklar
Copy link

asklar commented Aug 21, 2020

@TatianaKapos we miss youuuuuuu

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.

5 participants