mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-12 12:40:29 +08:00
* changes * css changes * updated PyPi version to 2.9b24 * Revert "updated PyPi version to 2.9b24" This reverts commit 48f678f491ef0c0479fc79b942d9de51740a9ded. * Revert "css changes" This reverts commit d31cd525a4f55f5c758872ff271c21b42e15feee. * Revert "changes" This reverts commit fadcb12ffeb6486fbf79cb20e7830f43ab5f2b79. * reverting * reverting * changes * changs * Revert "changs" This reverts commit 49d815f6fe50dca0dc8affdfe9d2b718e442b692. * Revert "changes" This reverts commit 481d7c21c4299d9f34207f3a30739cf14d922b2d. * changes * format * changes * format * test fix * test fix * test fix * fix tests Co-authored-by: Ali Abid <aliabid94@gmail.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 test_data 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.