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

[Bug] : Incomplete Paths for testcases for all steps inside tests folder #2

Open
arshpreet8051 opened this issue Mar 25, 2024 · 4 comments · May be fixed by #3
Open

[Bug] : Incomplete Paths for testcases for all steps inside tests folder #2

arshpreet8051 opened this issue Mar 25, 2024 · 4 comments · May be fixed by #3

Comments

@arshpreet8051
Copy link

arshpreet8051 commented Mar 25, 2024

Describe the issue

Issue while running tests from terminal eg. "npm run test : 1"
Getting error message "0-matches" for test
The paths for tests are not completely defined

To reproduce

  • Locate the directory
cd stylusdb-sql-base
  • Install Dependencies
npm i 
npm install jest --save-dev
  • Configure Jest
"scripts": {
  "test": "jest"
}
  • Run the command
npm run test:1

Expected Outcome

The result for test (pass or fail) should be the output instead of error message

Screenshot

image

@arshpreet8051 arshpreet8051 linked a pull request Mar 25, 2024 that will close this issue
1 task
@techsavvyash
Copy link
Member

techsavvyash commented Mar 28, 2024

Please share reproduction steps or minimum reproduction repository, can't reproduce on my system and getting normal behaviour on the base repo.
Maybe some setup or env issue on your system, would love to have feedback around this so that we can highlight the steps in the docs for others.

@arshpreet8051
Copy link
Author

arshpreet8051 commented Mar 31, 2024

Please share reproduction steps or minimum reproduction repository, can't reproduce on my system and getting normal behaviour on the base repo. Maybe some setup or env issue on your system, would love to have feedback around this so that we can highlight the steps in the docs for others.

Dear @techsavvyash ,

Thank you for your prompt response. I appreciate your attention to this matter. While I understand that the issue I encountered might not be replicable on your system, I'm confident that the changes I proposed will ensure compatibility across different environments.

The change I made in the code

(--testPathPattern=./tests/step-01)

to

(--testPathPattern=./tests/step-01/index)

resolved the issue on my system. By specifying the path more explicitly, I've ensured that the Jest tests will run consistently in every environment, regardless of individual configurations.

I'm more than willing to collaborate with you to find a solution that works for both of us. If there's any additional information or assistance I can provide, please don't hesitate to let me know.

Additionally, I believe it would be beneficial to update the project documentation with information about potential setup or environment issues. This could include a troubleshooting section or clarifications regarding the Jest configuration to help other users who might encounter similar problems in the future.

Thank you for your understanding and cooperation. I look forward to working together to resolve this issue.

Best regards,
@arshpreet8051


To provide more clarity on the problem, I've outlined the steps to reproduce the issue on my system below:

To reproduce

  • Locate the directory
cd stylusdb-sql-base
  • Install Dependencies
npm i 
npm install jest --save-dev
  • Configure Jest
"scripts": {
  "test": "jest"
}
  • Run the command
npm run test:1

Expected Outcome

The result for test (pass or fail) should be the output instead of error message

Screenshot

image

@techsavvyash
Copy link
Member

why are we installing and configuring jest separately, I think we already get it setup out of the box.

Saket-Kumar-Singh added a commit to status-20X/stylusdb-sql-assignment-Saket-Kumar-Singh that referenced this issue Apr 11, 2024
@sonustar
Copy link

sonustar commented May 4, 2024

Is this issue fixed @techsavvyash

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 a pull request may close this issue.

3 participants