-
Notifications
You must be signed in to change notification settings - Fork 2
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
#164489920 added test environment #3
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in the user test we have to use es6
That is true, I wrote it using ES5 because we do not have babel set up yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can set it up
I appreciate the way you configured mocha and test script, but I see that you have used es5. I think you'd have installed the needed packages to transpile es6 to es5, then use es6. The test script, I see that it run all file inside the test folder. I was wondering if we could specify the exact files. For example, I want the script to run files have |
Hello @cop1fab , I think that it can be better to have one commit per PR, thanks to set it |
@cop1fab, Good work. Please look into;
|
Thank you for the feedback, this is has been added to my priority list. |
3017235
to
993826b
Compare
4ed1369
to
6660179
Compare
1c8e353
to
e69e255
Compare
e69e255
to
dae8a08
Compare
dae8a08
to
d0f66b0
Compare
|
||
const server = http.createServer(app); | ||
app.listen(port, () => { | ||
console.log(`Server started successfully on ${port}`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unexpected console statement no-console
d0f66b0
to
a7e5478
Compare
Thank you Copain, for the PR, I appreciate the work you did and the effort you put in. But I see a lot of comments of HoundCI about the code style. Somewhere it comments that you missed semicolon and arrow-space. Just configure well eslint in your editor so that next time you'll take care of the code style. |
- testing environment added using mocha & chai [Delivers #164489920]
a7e5478
to
b94b5c1
Compare
# This is the 1st commit message: Update README.md # This is the commit message #2: updated README.md Added code climate badges. # This is the commit message #3: chore(Added test): Added test environment - testing environment added using mocha & chai [Delivers #164489920] # This is the commit message #4: Update package.json # This is the commit message #5: Add Heroku generated app.json # This is the commit message #6: Feature (token): setting token based authentication -config JWT token using package called json web token [Delivers #164489923] mend # This is the commit message #7: [feature#164489925] added user validation # This is the commit message #8: Feature (token): setting token based authentication -config JWT token using package called json web token [Delivers #164489923] mend # This is the commit message #9: Feature(login): Login via google -creating an application on google -configure google OAuth passport strategy [Delivers #164489928] # This is the commit message #10: Feature(login): Login via google -creating an application on google -configure google OAuth passport strategy [Delivers #164489928]
What does this PR do?
This PR sets unit testing; ensuring all implemented functionality is tested henceforth. This ensures the back end has all functionality working as intended.
Description of Task to be completed?
How should it be tested manually?
After cloning the repo, run
npm install to install all necessary dependencies then run npm run test
Pivotal Tracker story?
#164489920