mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-06 12:30:29 +08:00
* first draft * debug * add print * working oauth * inject OAuth profile + enable OAuth when expected + some doc * add changeset * mypy * opt * open in a new tab only from iframe * msg * add changeset * Apply suggestions from code review Co-authored-by: Abubakar Abid <abubakar@huggingface.co> * fix injection + gr.Error * allow third party cookie when possible * add button to sign in/sign out button * feedback changes * oauth as optional dependency * disable login/logout buttons locally * nothing * a bit of documentation * Add tests for Login/Logout buttons * Apply suggestions from code review Co-authored-by: Abubakar Abid <abubakar@huggingface.co> * mention required dependencies * fix package * fix tests * fix windows tests as well * Fake profile on local debug * doc * fix tets * lint * fix test * test buttons * login button fix * lint * fix final tests --------- Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com> Co-authored-by: Abubakar Abid <abubakar@huggingface.co> Co-authored-by: Hannah <hannahblair@users.noreply.github.com>
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 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.