gradio/test
Freddy Boulton 47d6231680
Always set queue=False if every is None for load events (#3391)
* Always set queue=False if every is None

* CHANGELOG + linting

* Move to latest release section

* changelog

---------

Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
2023-03-06 18:27:04 -07:00
..
golden
test_files Support large files try 2 (#3191) 2023-02-17 15:31:02 -08:00
tmp
__init__.py
conftest.py
README.md
requirements.in Sagemaker check (#3137) 2023-02-07 08:25:24 -08:00
requirements.txt Sagemaker check (#3137) 2023-02-07 08:25:24 -08:00
test_blocks.py Always set queue=False if every is None for load events (#3391) 2023-03-06 18:27:04 -07:00
test_components.py Dropdown Component Updates (#3211) 2023-02-23 16:32:18 -05:00
test_documentation.py
test_events.py Fix clear event (#3218) 2023-02-17 10:20:57 -05:00
test_examples.py Some improvements to Flag (#3289) 2023-02-28 10:29:34 -08:00
test_external.py Fix flaky external test (#3348) 2023-02-28 14:24:07 -05:00
test_flagging.py Some improvements to Flag (#3289) 2023-02-28 10:29:34 -08:00
test_interfaces.py fixing issue #3178 (#3227) 2023-03-06 11:27:47 -08:00
test_interpretation.py
test_mix.py
test_networking.py
test_pipelines.py
test_processing_utils.py Cache temp files created from base64 data (#3197) 2023-02-15 17:24:48 -06:00
test_queueing.py Add timeouts to queue messages (#3196) 2023-02-21 16:44:18 -05:00
test_reload.py
test_routes.py Access username from gr.Request class (#3296) 2023-02-24 11:40:34 -05:00
test_tunneling.py Persistent FRP (#3149) 2023-02-16 16:31:16 -06:00
test_utils.py Python backend to theming (#2931) 2023-03-06 12:52:31 -08: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.