mirror of
https://github.com/gradio-app/gradio.git
synced 2025-02-23 11:39:17 +08:00
1419538ea7
* asd * changes * fix everything * cleanup * add changeset * fix casing * lockfile * fix casing * fix ci, enable linting * fix test * add changeset * add changeset * delete changeset * fix dirs * fix casing * fix notebooks * fix casing * fix casing * fix casing * fix casing * fix casing * fix casing * fix casing * fix casing --------- Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com>
11 lines
893 B
Markdown
11 lines
893 B
Markdown
# 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.
|