The UI test are using different levels of abstraction and mocking for verifying different aspects of the UI.

The different nature of these approaches should be explained briefly in the developer documentation of the notebook-connector. Please see the presentation linked in "IntRef" for some inspiration.

• Add descriptive docstrings to example test cases
• Potentially enhance Developer guide to explain the different nature of these approaches in more detail

Examples

• test_run_line_magic_store_called calls get_access_store_ui directly
  • Can patch access_store_ui.get_ipython
  • Cannot take screenshots
• Tests using the fixtures solara_test, page_session, assert_solara_snapshot
  • Can take screenshots
  • cannot patch access_store_ui.get_ipython
• test_notebook_widget in file test/unit/ui/test_solara.py
  • uses fixture kernel_context
  • loads an app from a separate file to put it under test
  • Should be able to run store magic