Solved issue #3280

[Harshit-7373]

"npm run test" failing inside docker just after cloning the project #3280.

github-Harshit-7373

Fixes #issue-number

Changes:

1. After i run "npm run test" , it didn't run and showed that the jest command is not recognized.
2. I updated the jest dependencies to the latest and then run "npm run test"
3. It successfully runned without any issue , in the test status it showed 23 passed and total were 23.

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named and links to an issue number, i.e. Fixes #123

[raclim]

Thanks for your work on this!

I'm running the tests within my Docker environment with the Jest upgrade to 27.5.1 and am still running into my tests failing. Would you be able to provide more screenshots or a demonstrative video of how you're running it? Thanks!

[raclim]

Ideally, screenshots that help show an issue's resolution should be attached to the PR's description rather than as a folder within the codebase. It'd be great if you could remove this folder and screenshot and add the screenshot instead into your PR's description!

[raclim]

It would also be great if you could note any major changes you think are important to be aware of between version 27.3.1 to 27.5.1!

[Harshit-7373]

Actually , There are many issues that end up because of the version not been updated to up to date. And that is why i was thinking to modify the .env file and create a prebuild function before running the project where that javascript function will control the version control system. If the version differs in some or the other way , it can automatically run it , upgrade the version upto date so that unnecessary issues are not created . Need some views on this , if you could help me out. Also there is a way , to resolve this version issue using docker.

[Harshit-7373]

Ideally, screenshots that help show an issue's resolution should be attached to the PR's description rather than as a folder within the codebase. It'd be great if you could remove this folder and screenshot and add the screenshot instead into your PR's description!

Yes , I removed that folder , I understood my mistake and i can assure you this will not happen in the upcoming days.

[Harshit-7373]

Thanks for your work on this!

I'm running the tests within my Docker environment with the Jest upgrade to 27.5.1 and am still running into my tests failing. Would you be able to provide more screenshots or a demonstrative video of how you're running it? Thanks!

Sure , Just give me some time i will surely help you solve this issue.