mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-06 12:30:29 +08:00
* Implement Request class and its tests. * Add new requirements * Reformat codebase. * Fix formatting. * Add library level requirements. * Convert validated_data property to get_validated_data function. * Fix the client fixture. * Update test/test_utils.py * Update test/test_utils.py * Fix the client fixture. * Add missing initialization for Request._validated_data * Fix async test problem with test_tunneling.py * Update gradio/utils.py * Update gradio/utils.py * Fix formatting. Co-authored-by: Ömer Faruk Özdemir <farukozderim@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.