mirror of
https://github.com/gradio-app/gradio.git
synced 2025-03-25 12:10:31 +08:00
de997e67c9
* First pass at adding watermark to Video component * add changeset * Update video.py Space. * Adding demo files * linting * Automatically generated notebook generator * lint * Changing parentheses in check on whether conversion is needed * Unimportant comment/spacing changes * video * Update gradio/components/video.py Co-authored-by: Abubakar Abid <abubakar@huggingface.co> * Update gradio/components/video.py Co-authored-by: Abubakar Abid <abubakar@huggingface.co> * Update video.py Adding more details on watermark_file. * Update gradio/components/video.py Change in and/or statement. Co-authored-by: Abubakar Abid <abubakar@huggingface.co> * Updating handling of WASM. * Add paren. * Minor lint change: if instead of elif * lint change: spacing * tweaks * fixes * demo * demos * notebooks * notebooks * remove comments * video --------- Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com> Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
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.