status-20X / stylusdb-sql-base

Base repository with just follow along documentation to build your own StylusDB SQL.
GNU Lesser General Public License v2.1
3 stars 2k forks source link

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

Open arshpreet8051 opened 7 months ago

arshpreet8051 commented 7 months ago

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

"scripts": {
  "test": "jest"
}

Expected Outcome

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

Screenshot

image

techsavvyash commented 7 months ago

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 commented 7 months ago

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

"scripts": {
  "test": "jest"
}

Expected Outcome

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

Screenshot

image

techsavvyash commented 7 months ago

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

sonustar commented 6 months ago

Is this issue fixed @techsavvyash