Skip to content

Moves integration test at top level with jasmine #593

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 7 commits into from
Jul 26, 2018

Conversation

flovilmart
Copy link
Contributor

  • Use jasmine so toolchain is similar to parse-server
  • Replaces bash script with pre-test

- Use jasmine so toolchain is similar to parse-server
- Replaces bash script with pre-test
@flovilmart flovilmart force-pushed the use-jasmine-no-mocha branch from 9bc3b14 to 924f8ab Compare July 4, 2018 20:26
@codecov
Copy link

codecov bot commented Jul 4, 2018

Codecov Report

Merging #593 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #593   +/-   ##
=======================================
  Coverage   84.57%   84.57%           
=======================================
  Files          48       48           
  Lines        4039     4039           
  Branches      911      911           
=======================================
  Hits         3416     3416           
  Misses        623      623
Impacted Files Coverage Δ
src/LiveQueryClient.js 86.66% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25d13ed...17b2616. Read the comment docs.

@flovilmart flovilmart requested a review from dplewis July 6, 2018 10:06
Copy link
Member

@dplewis dplewis left a comment

Choose a reason for hiding this comment

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

Just a few more nits. I was able to install VSCode and the Extensions. I'll have to get used to using it tho.

CONTRIBUTING.md Outdated
@@ -1,35 +1,60 @@
# Contributing to the Parse JavaScript SDK
We want to make contributing to this project as easy and transparent as possible.

If you're looking to get started, but want to ease yourself into the codebase, look for issues tagged [good first bug](https://github.com/ParsePlatform/Parse-SDK-JS/labels/good%20first%20bug). These are simple yet valuable tasks that should be easy to get started.
If you're looking to get started, but want to ease yourself into the codebase, look for issues tagged [good first bug](https://github.com/parse-community/Parse-SDK-JS/labels/good%20first%20bug). These are simple yet valuable tasks that should be easy to get started.
Copy link
Member

Choose a reason for hiding this comment

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

There isn't a good first bug label there is a good first task

https://github.com/parse-community/Parse-SDK-JS/labels/good%20first%20task

CONTRIBUTING.md Outdated
### Recommended setup:

* [vscode](https://code.visualstudio.com), the popular IDE.
* [Jest Extesnsion](https://marketplace.visualstudio.com/items?itemName=Orta.vscode-jest) the Jest extension for vscode to run the tests inline and debug quicky.
Copy link
Member

Choose a reason for hiding this comment

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

Extension*

CONTRIBUTING.md Outdated
@@ -40,27 +65,32 @@ Not all issues are SDK issues. If you're unsure whether your bug is with the SDK
Details are key. The more information you provide us the easier it'll be for us to debug and the faster you'll receive a fix. Some examples of useful tidbits:

* A description. What did you expect to happen and what actually happened? Why do you think that was wrong?
* A simple unit test that fails. Refer [here][tests-dir] for examples of existing unit tests. See our [README](README.md#usage) for how to run unit tests. You can submit a pull request with your failing unit test so that our CI verifies that the test fails.
* A simple unit test that fails. Refer [here][tests-dir] for examples of existing unit tests and [here](integration-test-dir) for integration tests examples. See for how to setup your machine and run unit tests in [this]() guide. You can submit a pull request with your failing unit test so that our CI verifies that the test fails.
Copy link
Member

Choose a reason for hiding this comment

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

Most of the links here are broken...

@flovilmart
Copy link
Contributor Author

Thanks for the review @dplewis, i’ll Fix up before end of week

@flovilmart flovilmart force-pushed the use-jasmine-no-mocha branch from 20739c2 to 6b118ff Compare July 17, 2018 08:27
@flovilmart
Copy link
Contributor Author

@dplewis I fixed the links, and checked them, let me know!

Copy link
Member

@dplewis dplewis left a comment

Choose a reason for hiding this comment

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

nit

CONTRIBUTING.md Outdated
[rest-api]: https://www.parse.com/docs/rest/guide
[stack-overflow]: http://stackoverflow.com/tags/parse-server
[bug-reports]: https://github.com/parse-community/parse-server/issues
[rest-api]: https://docs.parseplatform.org/rest/guide
[parse-api-console]: http://blog.parse.com/announcements/introducing-the-parse-api-console/
Copy link
Member

Choose a reason for hiding this comment

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

@dplewis
Copy link
Member

dplewis commented Jul 26, 2018

@flovilmart Whats the status here?

@flovilmart
Copy link
Contributor Author

@dplewis that looks all good!

@dplewis dplewis merged commit 358a335 into master Jul 26, 2018
@dplewis dplewis deleted the use-jasmine-no-mocha branch July 26, 2018 19:51
@dplewis
Copy link
Member

dplewis commented Jul 28, 2018

@flovilmart In parse-server you added npm run watch would it be possible to add it here.

When I'm testing I only need to rebuild node, not browser / react. Its kinda time consuming.

@flovilmart
Copy link
Contributor Author

flovilmart commented Jul 28, 2018

Ah right, I believe that should be easy feasible, as it’s gulp based, with gulp-watch you should be able to craft something easily https://www.npmjs.com/package/gulp-watch

edit: nothing is easy

@dplewis
Copy link
Member

dplewis commented Jul 28, 2018

Can you add it? 🙏

My knowledge of gulp is a little above zero.

Currently I'm having this error

[12:15:37] Starting 'browserify'...
[12:15:38] The following tasks did not complete: browserify
[12:15:38] Did you forget to signal async completion?

@flovilmart
Copy link
Contributor Author

Uhm yeah I'll need to have a look, but it's gonna be later today, busy on something else now ;) Would be faster for you to learn gulp :P

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.

2 participants