Error running backend tests
See original GitHub issueI ran backend test
bash scripts/run_backend_tests.sh
Excecption: WARNING 👍 WARNING: FAILED TO RUN TESTS. This is most likely due to an import error. No test’s were run
- I am using linux mint and Python 3.4.3
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Unable to run backend tests · Issue #10064 - GitHub
I used this command to run a backend test python -m scripts.run_backend_tests --test_target=scripts.linters.general_purpose_linter_test ERROR LOG Error 1 ...
Read more >Backend Testing: What Is It and How It's Done at EGO
Depending on the answer, the user proceeds to the app's main page or gets a warning/error message. As a software testing services company,...
Read more >Unable to contact test backend running in app. A common ...
SetUp : System.Exception : Unable to contact test backend running in app. A common cause is that the app is not properly linked...
Read more >Running tests with Jest: getting an error with TypeScript config ...
I'm using NodeJS, TypeORM with TypeScript. I'm getting this error when running yarn test : Error: Jest: Failed to parse the TypeScript config...
Read more >Fullstack part4 | Testing the backend
We will now start writing tests for the backend. Since the backend does not contain any complicated logic, it doesn't make sense to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@seanlip In
I tried printing os.environ.get(‘PYTHONPATH’), and it showed none. Is the problem somewhere here ?
Please bring someone to rescue to get this issue solved for me , im unable to issue a PR due to this issue 😦
Closing, since this is a local issue that no one else has reported and that we cannot reproduce.