From 9397234031ca056d7200aa8bed35420ed4121983 Mon Sep 17 00:00:00 2001 From: Vadzim Hushchanskou Date: Wed, 12 Nov 2025 12:20:56 +0300 Subject: [PATCH 1/2] Update pytest.md --- .../test-framework-integration/Python/pytest.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/docs/log-data-in-reportportal/test-framework-integration/Python/pytest.md b/docs/log-data-in-reportportal/test-framework-integration/Python/pytest.md index 855c1c953b..ab5487cedf 100644 --- a/docs/log-data-in-reportportal/test-framework-integration/Python/pytest.md +++ b/docs/log-data-in-reportportal/test-framework-integration/Python/pytest.md @@ -30,10 +30,20 @@ Create the configuration file `pytest.ini` in the root directory of tests, or al The `pytest.ini` file should have next mandatory fields: -- `rp_api_key` - value could be found in the User Profile section - `rp_project` - name of project in ReportPortal - `rp_endpoint` - address of ReportPortal Server +And one type of authorization: API Key or OAuth 2.0 Password grant. You can do this by setting: +- `rp_api_key` or `RP_API_KEY` environment variable. You can get it in the User Profile section on the UI. + +Or: +- `rp_oauth_uri` - OAuth 2.0 token endpoint URL for password grant authentication. **Required** if API key is not used. +- `rp_oauth_username` - OAuth 2.0 username for password grant authentication. **Required** if OAuth 2.0 is used. +- `rp_oauth_password` - OAuth 2.0 password for password grant authentication. **Required** if OAuth 2.0 is used. +- `rp_oauth_client_id` - OAuth 2.0 client identifier. **Required** if OAuth 2.0 is used. +- `rp_oauth_client_secret` - OAuth 2.0 client secret. **Optional** for OAuth 2.0 authentication. +- `rp_oauth_scope` - OAuth 2.0 access token scope. **Optional** for OAuth 2.0 authentication. + Example of `pytest.ini`: ```python @@ -47,8 +57,6 @@ Example of `pytest.ini`: rp_ignore_attributes = 'xfail' 'usefixture' ``` -- The `rp_api_key` can also be set with the environment variable `RP_API_KEY`. This will override the value set for `rp_api_key` in pytest.ini - The following parameters are optional: - `rp_client_type = SYNC` - Type of the under-the-hood ReportPortal client implementation. Possible values: [SYNC, ASYNC_THREAD, ASYNC_BATCHED]. @@ -65,7 +73,7 @@ The following parameters are optional: - `rp_connect_timeout = 15` - Connection timeout to ReportPortal server. Default value is "10.0". - `rp_read_timeout = 15` - Response read timeout for ReportPortal connection. Default value is "10.0". - `rp_log_batch_size = 20` - size of batch log request. -- `rp_log_batch_payload_size = 65000000` - maximum payload size in bytes of async batch log requests. +- `rp_log_batch_payload_limit = 65000000` - maximum payload size in bytes of async batch log requests. - `rp_log_level = INFO` - The log level that will be reported. - `rp_log_format = [%(levelname)7s] (%(name)s) %(message)s (%(filename)s:%(lineno)s)` - Format string to be used for logs sent to the service. - `rp_ignore_attributes = 'xfail' 'usefixture'` - Ignore specified pytest markers. From edd4f2af0715d12b39d665aefe470bff8b298510 Mon Sep 17 00:00:00 2001 From: Yuliya Prihodko <107035036+pressayuliya@users.noreply.github.com> Date: Thu, 20 Nov 2025 11:38:57 +0300 Subject: [PATCH 2/2] EPMRPP-109709 || Update MCP Server doc (#1031) Co-authored-by: Yuliya_Prihodko --- docs/external-integrations/MCPServer.mdx | 136 +++++++++++++++-------- 1 file changed, 90 insertions(+), 46 deletions(-) diff --git a/docs/external-integrations/MCPServer.mdx b/docs/external-integrations/MCPServer.mdx index 3204ef713c..73d37e2bbe 100644 --- a/docs/external-integrations/MCPServer.mdx +++ b/docs/external-integrations/MCPServer.mdx @@ -16,20 +16,99 @@ ReportPortal MCP Server allows to receive summaries of launches and perform vari Available tools: -1. Run Unique Error Analysis. -2. Run Quality Gate. -3. Run Auto-Analysis. -4. Get Test Items by Filter. -5. Get Launches. -6. Launch Force Finish. -7. Launch Delete. -8. Get Test Item Logs by Filter. -9. Get Test Item by ID. -10. Get Test Item Attachments. -11. Get Last Launch by Name. +1. Run Unique Error Analysis +2. Run Quality Gate +3. Run Auto-Analysis +4. Get Test Items by Filter +5. Get Launches +6. Launch Force Finish +7. Launch Delete +8. Get Test Item Logs by Filter +9. Get Test Item by ID +10. Get Test Item Attachments +11. Get Last Launch by Name +12. Get Project Defect Types +13. Update defect types by item IDs ## Usage with your favorite AI tools +Below are brief setup instructions for configuring the ReportPortal MCP Server with Cursor, Copilot, and Claude Desktop. + +### Cursor IDE + +#### Local installation + +To configure ReportPortal MCP Server with Cursor: + +1. Log in to Cursor. +2. Open Settings. +3. Select "Tools & Integrations" section. +4. Click "New MCP Server". + + + +5. Fill in the required fields in the Config file. + + + +6. The list of available tools appears. + + + +#### Remote server + +This setup allows Cursor to communicate with a remote ReportPortal MCP Server. + +```json +{ + "mcpServers": { + "reportportal": { + "url": "http://your-mcp-server-host:port/mcp/", + "headers": { + "Authorization": "Bearer your-api-token", + "X-Project": "YourProjectInReportPortal" + } + } + } +} +``` + +### GitHub Copilot + +#### Local installation + +To configure ReportPortal MCP Server with Copilot: + +1. Log in to Copilot. +2. Type ">mcp" in the search bar. +3. Select "MCP: Open User Configuration" option. + + + +4. Fill in the required fields in the Config file. + + + +#### Remote server + +Use this configuration to connect Copilot to a remote ReportPortal MCP Server. + +```json +{ + "servers": { + "reportportal": { + "url": "http://your-mcp-server-host:port/mcp/", + "requestInit": { + "headers": { + "Authorization": "Bearer your-api-token", + "X-Project": "YourProjectInReportPortal" + } + } + } + } +} +``` + ### Claude Desktop To configure ReportPortal MCP Server with Claude: @@ -78,41 +157,6 @@ Token is API Key the user's Profile page. -Below are brief setup instructions for configuring the ReportPortal MCP Server with Cursor and Copilot. - -### Cursor IDE - -To configure ReportPortal MCP Server with Cursor: - -1. Log in to Cursor. -2. Open Settings. -3. Select "Tools & Integrations" section. -4. Click "New MCP Server". - - - -5. Fill in the required fields in the Config file. - - - -6. The list of available tools appears. - - - -### GitHub Copilot - -To configure ReportPortal MCP Server with Copilot: - -1. Log in to Copilot. -2. Type ">mcp" in the search bar. -3. Select "MCP: Open User Configuration" option. - - - -4. Fill in the required fields in the Config file. - - - Refer to the detailed user guide for the [full setup instructions](https://github.com/reportportal/reportportal-mcp-server) of the MCP Server. Whether you're aiming to optimize test analysis or simplify routine QA tasks, MCP empowers your AI tools to act with clarity and precision.