mirror of
https://github.com/gradio-app/gradio.git
synced 2025-03-31 12:20:26 +08:00
* handle pasted text as file * test * add changeset * remove unneeded test * update file UI * add changeset * Revert "handle pasted text as file" This reverts commit 1910029f103f89573210ee0a8b62823505a1b1db. * add changeset * Revert "test" This reverts commit 25c17bd8d3505d09cd571382afeeacdec197bd9c. * story * remove border * Revert "add changeset" This reverts commit 29a91ee9dff771663c414880d10815ffe2f6b961. * add changeset * add code * Code * add code * add changeset * Update solid-hands-nail.md * code * add metadata typecheck * trigger ci * remove thought css * Revert "remove thought css" This reverts commit f1ea8f88f6ced9dc8e8897abdfd529952f851954. * fix tuples - add borders * lint * Fix typecheck * css tweak * add code * fix parameter name --------- Co-authored-by: Hannah <hannahblair@users.noreply.github.com> Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com>
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.