add better info about how to write a complete test

website/documentation/content/user_documentation.py

@@ -10,9 +10,9 @@ def user_fixture():
     ui.markdown('''
         We recommend utilizing the `user` fixture instead of the [`screen` fixture](/documentation/screen) wherever possible
         because execution is as fast as unit tests and it does not need Selenium as a dependency
-        when loaded via `pytest_plugins = ['nicegui.testing.user_plugin']`
-        (see [project structure](/documentation/project_structure)).
+        when loaded via `pytest_plugins = ['nicegui.testing.user_plugin']`.
         The `user` fixture cuts away the browser and replaces it by a lightweight simulation entirely in Python.
+        See [project structure](/documentation/project_structure) for a description of the setup.
 
         You can assert to "see" specific elements or content, click buttons, type into inputs and trigger events.
         We aimed for a nice API to write acceptance tests which read like a story and are easy to understand.
@@ -23,12 +23,13 @@ def user_fixture():
     with python_window(classes='w-[600px]', title='example'):
         ui.markdown('''
             ```python
-            await user.open('/')
-            user.find('Username').type('user1')
-            user.find('Password').type('pass1').trigger('keydown.enter')
-            await user.should_see('Hello user1!')
-            user.find('logout').click()
-            await user.should_see('Log in')
+            async def test_login(user: User) -> None:
+                await user.open('/')
+                user.find('Username').type('user1')
+                user.find('Password').type('pass1').trigger('keydown.enter')
+                await user.should_see('Hello user1!')
+                user.find('logout').click()
+                await user.should_see('Log in')
             ```
         ''')