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

Issues in testing #161

Open
ksraj123 opened this issue Jul 29, 2020 · 3 comments
Open

Issues in testing #161

ksraj123 opened this issue Jul 29, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@ksraj123
Copy link
Contributor

Describe the bug

  • EADDRINUSE, error address in use error in all tests files after the first test file
  • In addition to issues described in Fix failing test cases in the user route. #152 user route has another failing test case which 400 expected 200
  • Test cases failing in org route, multiple 404s
  • Test cases failing in proposal route
  • Jest does not exit

To Reproduce
Steps to reproduce the behaviour:

  1. npm run test

Expected behaviour

  • EADDRINUSE error should not be present in any test file
  • Failing test case in user route should get expected value 200 instead of current 400
  • All test cases should pass
  • Jest should exit successfully upon completion of tests whatever may be the results.

Screenshots

  • EADDRINUSE
    Screenshot from 2020-07-29 03-44-00

  • 400 in user route
    Screenshot from 2020-07-29 03-52-20

  • Erros in org route
    Screenshot from 2020-07-29 03-46-26

  • Test cases failing in proposal route
    Screenshot from 2020-07-29 03-42-44

  • Jest not exiting
    Screenshot from 2020-07-29 03-45-24

Additional context
Working on this.

@ksraj123 ksraj123 added the bug Something isn't working label Jul 29, 2020
@ksraj123 ksraj123 mentioned this issue Jul 29, 2020
11 tasks
@ksraj123
Copy link
Contributor Author

Fixed in #160

@Rupeshiya
Copy link
Member

Include this too #137

@Rupeshiya
Copy link
Member

Working on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants