mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-06 12:30:29 +08:00
51e241addd
* network idle
* Use **/upload
* Test flakes
* Fix pythont tests
* add changeset
* Use right wait
* upload
* trigger ci
* swap order
* networkidle❓
* lint'
* df
* 2 workers
* networkidle
* Fix cli test
* pause
* 3.8 fix
* 3.8
* no promise.all
* trigger ci
* Add code
* mark xfail
* trigger ci
* timeout
* Empty
* Flake
* test
* Flakes
* change test
* awaits
* cleanup
* fixes
---------
Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com>
Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
Backend Testing Guidelines
- All the tests should test Backend functionalities. Frontend functionalities and e2e tests are done in Frontend.
- Make use of pytest fixtures whenever it is possible. With fixtures, objects with high initialize durations are reused within tests, ex. a client session.
- All testdata resides within _gradio/test_data and all test_files resides within test/test_files.
- When doing network operations do not forget to make use of async to make tests faster.
- Have clear class and function naming within the tests.
- Short descriptions within test functions are great.
- Library function docstrings is expected to contain an example, please add missing docstrings to the library while you are writing tests the related function.
- Library docstring examples and descriptions are expected to align with tests, please fix divergent tests and library docstrings.