mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-18 12:50:30 +08:00
54af6ae290
* v2 version now accepts video and subtitle format inputs. * remove debug log and some format issue * Update CHANGELOG.md * Upload components.py and regenerate demo * fix components and add comment to function * fix postprocess return format * changelog * demo change to gr.Interface type * fix file_types * fixes * added video serializer * clean up preprocess * clean up postprocess * formatting * frontend * fixed serialization * dataclass * fix serialize * version * fix tests * version * changelog * typing * version * changelog * version * versin * fix tests * fix tests * backend * test * changes * relax test * fix demo * notebook * changes * fix * changes * Update gradio/components.py * Update client/python/gradio_client/client.py --------- Co-authored-by: Abubakar Abid <abubakar@huggingface.co> Co-authored-by: Ali Abid <aabid94@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.