Freddy Boulton 96c17a7470
Add support for async generators (#3821)
* Add impl + unit test

* CHANGELOG

* Lint

* Type check

* Remove print

* Fix tests

* revert change

* Lint

* formatting

* Fix test

* Lint

---------

Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
Co-authored-by: Ali Abid <aabid94@gmail.com>
2023-05-08 23:21:47 -05:00
..
2022-03-17 10:45:48 -07:00
2022-03-30 13:08:34 +03:00
2022-04-14 00:06:14 +03:00
2023-05-04 21:54:23 -05:00
2023-04-03 15:48:18 -07:00
2023-05-04 21:54:23 -05:00
2023-05-04 21:54:23 -05:00
2023-05-04 21:54:23 -05:00
2023-05-04 21:54:23 -05:00
2023-01-16 12:17:41 -05:00
2023-02-16 16:31:16 -06:00
2023-05-04 21:54:23 -05:00

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.