-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
review tests #1138
Comments
I'm looking on the test with pytest-reverse and do prepare a conda-forge package of that too |
* skipped test_version_name_delete * tests skipped, because they can be biased * ToDos added * skipped because failing in reverse order * test assert removed * hanging tests skipped * a few tests skipped which fails in (reverse) order * skipped because: An unhandled message box popped up during your test! * simplified tests * removed dependency to server start * improved tests for user object, refactored test_files * refactored test_files_api * Test_Init_Server refactored * server tests partial refactored * test_server completed * fixed type bug in server and updated test_server * cleanup duplicated tests * reactored test_server * refactored test_utils * refactored test_chat_manager.py for test_client * refactored to test_client * test_file_manager refactored for test_client * refactored test_files to test_client * test_files_api refactored for test_client * refactored test_seed for test_client * refactored call of db.init_app * used userdata * removed duplications * enabled skipped tests * introduces reverse order on testing * disabled a test, because of KeyError * renamed the "json" parameter * tests start with a resetted database
There are some more to do, please leave this issue open. |
@matrss I think you can later close this. |
15 skipped tests get re-enabled in #2165, but there are another 11 tests that are still skipped afterwards. Those are either incomplete, outdated, can not be run with other tests due to specific config requirements (basic auth) or break other tests in ways that I wasn't able to fix. So this issue isn't entirely solved yet. |
While there are remaining tests that should be re-visited I think a lot has already been done on develop and the rest is not as pressing as to block a major release, so I'll push this back to v10. |
We recognized some tests still depend on others. order one by one.
In a first step these get skipped with a refactoring remark.
The next step is to refactor them.
The text was updated successfully, but these errors were encountered: