Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move test files next to implementation files
See original GitHub issueRight now we have (almost) all tests files in the /tests/ subdirectory, yet it seems more logical and convenient to keep them next to the corresponding code they’re testing. This issue is about simply moving those files (with git mv) and patching any imports that may need it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to move tests into a separate file for binaries in Rust's ...
You need to create an src/lib.rs and move the functions you want to test piecemeal. Then you'll be able to use extern crate...
Read more >Best practices for test files in Go and Java - Symflower
Best practices for where to store and name test files with Go and Java, and how to configure them in Symflower.
Read more >Working and unit testing with temporary files in Java
Temporary files are frequently used in testing and in production. Here is how to create and manage—and delete—them.
Read more >Organizing Tests in Jest - Medium
Putting all of your test code into a neatly organized /tests directory. · Putting your test code next to the files they are...
Read more >Splitting Our Tests into Multiple Files, and a Generic Wait Helper
We've split our functional tests nicely out into different files. Next we'll start writing our FT, but before long, as you may be...
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 Free
Top 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
Think this is part of a Google or TF style guide, although can’t find a good link for it
Note, testing files should be stylized according to the TF style guide (pylintrc file) in #474 as they’re moved into the main
tf_encryptedpackage (or any other package that’s being run during the lint part of the Makefile)