mirror of
https://github.com/gradio-app/gradio.git
synced 2024-12-21 02:19:59 +08:00
| .. | ||
| golden | ||
| test_files | ||
| tmp | ||
| __init__.py | ||
| README.md | ||
| requirements.in | ||
| requirements.txt | ||
| test_blocks.py | ||
| test_components.py | ||
| test_encryptor.py | ||
| test_external.py | ||
| test_flagging.py | ||
| test_inputs.py | ||
| test_interfaces.py | ||
| test_interpretation.py | ||
| test_mix.py | ||
| test_networking.py | ||
| test_outputs.py | ||
| test_process_examples.py | ||
| test_processing_utils.py | ||
| test_queuing.py | ||
| test_routes.py | ||
| test_tunneling.py | ||
| test_utils.py | ||
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.