You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCode has a separate section for tests and it lists all the tests in the project (see attached image). This is very useful for debugging. This feature would be easier to use if the names for the Class objects in the various tests.py files follow a consistent naming scheme. One possibility is to name all the classes "LoadTestCases" since the majority of the existing tests already use this name. Another possibility is to use "folder-name_tests", for example Kompsat_Tests, Fast_Tests, and so on. This is an easy change to make, and as far as I know, it does not affect anything else.
The text was updated successfully, but these errors were encountered:
Yes, it would probably be good to make these more descriptive. I know I'm frequently guilty of just cloning a test.py file and replacing the test methods....at the very least, the class names should include the project name or category the tests are meant to be exercising.
This is a minor issue which is easy to fix.
VSCode has a separate section for tests and it lists all the tests in the project (see attached image). This is very useful for debugging. This feature would be easier to use if the names for the Class objects in the various tests.py files follow a consistent naming scheme. One possibility is to name all the classes "LoadTestCases" since the majority of the existing tests already use this name. Another possibility is to use "folder-name_tests", for example Kompsat_Tests, Fast_Tests, and so on. This is an easy change to make, and as far as I know, it does not affect anything else.
The text was updated successfully, but these errors were encountered: