mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-18 12:50:30 +08:00
* Delete state
* add changeset
* Delete state
* WIP
* Add load event
* Working ttl
* unload e2e test
* Clean up
* add changeset
* Fix notebook
* add changeset
* Connect to heartbeat in python client
* 15 second heartbeat
* Demo for unload
* Add notebook
* add changeset
* Fix docs
* revert demo changes
* Add docstrings
* lint 🙄
* Edit
* handle shutdown issue
* state comments
* client test
* Fix:
* Fix e2e test
* 3.11 incompatibility
* delete after one hour
* lint + highlight
* Update .changeset/better-tires-shave.md
Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
* Update .changeset/better-tires-shave.md
Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
---------
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 reside 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.