It’s very simple! If you’re not familiar with pytest-testmon it’s probably the right time to read the (short) docs and try testmon locally. The local collection of data and compatibility with various plugins is battle tested by the thousands of users who use it every day. With version 2.0 pytest-testmon became a client for testmon.net.
By becoming a part of the private beta you received a tmnet_api_key for each project which you want to enroll. You have to add this to your configuration for pytest (pytest.ini, pyproject.toml or any other place where you configure your pytest https://docs.pytest.org/en/7.1.x/reference/customize.html)
e.g.
# pytest.ini
[pytest]
tmnet_api_key = projectname_b0f74c20b0684cf19a51bbec6fae63bb
# ...
or
# pyproject.toml
[tool.pytest.ini_options]
tmnet_api_key = "projectname_b0f74c20b0684cf19a51bbec6fae63bb"
# ...
The new --tmnet argument keeps all the existing functionality and testmon
arguments but switches the persistence from .testmondata
to testmon.net. --tmnet implies --testmon and all the other
arguments like --testmon-noselect, --testmon-forceselect, --testmon-nocollect can be
also used and work the same as if you worked locally. There is no synchronization between
local .testmondata and testmon.net