mirror/gradio
2
0
Fork 0
mirror of https://github.com/gradio-app/gradio.git synced 2025-02-11 11:19:58 +08:00
Code Issues Packages Projects Releases Wiki Activity
16826ee9cc
gradio/test
History
aliabid94 16826ee9cc
Fix broken API page (#1919) 
* chagnes

* frontend_fix

* changes

* changes

* changes

* changes

* changes

* fixed typing

Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
2022-08-01 18:15:55 -07:00
..
golden
test_files Model3d fix (#1342) 2022-05-20 17:53:27 -07:00
tmp
__init__.py
conftest.py Mark tests as flaky and run in separate job (#1735) 2022-07-11 13:20:11 -04:00
README.md
requirements.in Add python-3.7 tests (#1818) 2022-07-19 10:48:46 -04:00
requirements.txt Add python-3.7 tests (#1818) 2022-07-19 10:48:46 -04:00
test_blocks.py integrate() method moved to Blocks (#1776) 2022-07-18 22:47:40 -07:00
test_components.py Always return headers from postprocess (#1893) 2022-08-01 15:57:31 -07:00
test_documentation.py Fix broken API page (#1919) 2022-08-01 18:15:55 -07:00
test_encryptor.py
test_examples.py Exposing examples as a component for Blocks (#1639) 2022-07-06 11:23:35 -07:00
test_external.py Mark tests as flaky and run in separate job (#1735) 2022-07-11 13:20:11 -04:00
test_flagging.py
test_interfaces.py Exposing examples as a component for Blocks (#1639) 2022-07-06 11:23:35 -07:00
test_interpretation.py
test_mix.py Mark tests as flaky and run in separate job (#1735) 2022-07-11 13:20:11 -04:00
test_networking.py
test_processing_utils.py
test_queuing.py
test_routes.py
test_tunneling.py fix tunneling test (#1694) 2022-07-04 17:04:44 +03:00
test_utils.py Add python-3.7 tests (#1818) 2022-07-19 10:48:46 -04:00

README.md

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.