reportportal · maria-hambardzumian · May 7, 2026 · Apr 29, 2026 · May 6, 2026 · May 7, 2026
@@ -27,6 +27,7 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
+          ref: master
           token: ${{ secrets.GH_TOKEN }}
 
       - name: Set up Node.js

@@ -71,6 +71,7 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
+          ref: master
           token: ${{ secrets.GH_TOKEN }}
 
       - name: Set up Node.js

@@ -27,6 +27,7 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
+          ref: master
           token: ${{ secrets.GH_TOKEN }}
 
       - name: Set up Node.js

@@ -16,13 +16,12 @@ Auto-analysis performs automated defect triaging and defines the reason for the
 
 The process of Auto-Analysis is based on previous user-investigated users' results using Machine Learning.
 
-An auto-analyzer is presented by a combination of several services: OpenSearch and Analyzer service (two instances Analyzer and Analyzer train).
+An auto-analyzer is presented as a combination of several services: OpenSearch and the Analyzer service.
 
-* OpenSearch contains an analytical base and stores training data for retraining of models.
-* Analyzer instance performs all operations, connected with the basic functionality (indexing/removing logs, searching logs, auto-analysis,  ML suggestions).
-* Analyzer train instance is responsible for training models for Auto-analysis and ML suggestions functionality.
+* OpenSearch contains the analytical database and stores training data for model retraining.
+* The Analyzer performs all operations related to the core functionality (indexing/removing logs, log search, auto-analysis, ML suggestions, as well as training models for auto-analysis and ML suggestions).
 
-*You have the option to disable the Analyzer by removing the Analyzer and Analyzer train services from the installation.*
+*You have the option to disable the Analyzer by removing the Analyzer service from the installation.*
 
 There are several ways to use an analyzer in our test automation reporting dashboard:
 

@@ -1,9 +1,18 @@
 ---
 sidebar_position: 4
 sidebar_label: Improving test automation stability
+title: Improving test automation stability
 description: Learn how ReportPortal improve test automation stability, reduced failures, and cut analysis time with better logging, triage, and dashboards.
 ---
 
+<head>
+  <meta name="robots" content="noindex,follow" />
+  <link
+    rel="canonical"
+    href="https://reportportal.io/case-studies/improving-test-automation-stability/"
+  />
+</head>
+
 # Improving test automation stability
 
 **Challenges**
@@ -29,4 +38,7 @@ By integrating the test framework with ReportPortal.io, EPAM's team provided:
 - Reduced test automation results analysis effort by 45%
 - Provided clear and comprehensive test automation reporting dashboard: number of test cases, regression passing rate, reasons for failures, product status
 
-<MediaViewer src={require('./img/CaseStudy4.png')} alt="Case Study Improving test automation stability thank to our test automation reporting dashboard" />
+<MediaViewer
+  src={require('./img/CaseStudy4.png')}
+  alt="Case Study Improving test automation stability thank to our test automation reporting dashboard"
+/>
@@ -1,9 +1,18 @@
 ---
 sidebar_position: 2
 sidebar_label: Increasing test automation stability and visibility
+title: Increasing test automation stability and visibility
 description: Discover how ReportPortal boosted test stability from 25% to 95%, cut analysis effort by 90%, and improved visibility for smarter release decisions.
 ---
 
+<head>
+  <meta name="robots" content="noindex,follow" />
+  <link
+    rel="canonical"
+    href="https://reportportal.io/case-studies/increasing-test-automation-stability-and-visibility/"
+  />
+</head>
+
 # Increasing test automation stability and visibility
 
 **Challenges**
@@ -33,4 +42,7 @@ Integration with ReportPortal.io allowed the client to:
 - Client stakeholders use ReportPortal.io data to make release decisions
 - ReportPortal.io became the main tool for tracking test automation progress and health
 
-<MediaViewer src={require('./img/CaseStudy2.png')} alt="Case Study Increasing test automation stability and visibility thanks to our test report&analytics dashboard" />
+<MediaViewer
+  src={require('./img/CaseStudy2.png')}
+  alt="Case Study Increasing test automation stability and visibility thanks to our test report&analytics dashboard"
+/>
@@ -1,9 +1,17 @@
 ---
 sidebar_position: 3
 sidebar_label: Reducing regression analysis efforts
+title: Reducing regression analysis efforts
 description: Discover how ReportPortal reduces regression analysis time by enabling real-time insights, automated reruns, and a powerful QA metrics dashboard for faster, smarter testing.
 ---
 
+<head>
+  <meta name="robots" content="noindex,follow" />
+  <link
+    rel="canonical"
+    href="https://reportportal.io/case-studies/reducing-regression-analysis-efforts/"
+  />
+</head>
 
 # Reducing regression analysis efforts
 
@@ -27,4 +35,7 @@ description: Discover how ReportPortal reduces regression analysis time by enabl
 - Improved task management due to possibility to plan work allocation and track tests assigned to each team member
 - Real-time dashboards were tailored to client’s KPIs, giving full transparency of test execution results
 
-<MediaViewer src={require('./img/CaseStudy3.png')} alt="Case Study Reducing regression analysis efforts thanks to our qa automation dashboard" />
+<MediaViewer
+  src={require('./img/CaseStudy3.png')}
+  alt="Case Study Reducing regression analysis efforts thanks to our qa automation dashboard"
+/>
@@ -1,9 +1,17 @@
 ---
 sidebar_position: 1
 sidebar_label: Reducing regression time by 50%
+title: Reducing regression time by 50%
 description: Learn how to reduce regression time by 50% using ReportPortal's test automation reporting tools and qa dashboard tools for faster analysis.
 ---
 
+<head>
+  <meta name="robots" content="noindex,follow" />
+  <link
+    rel="canonical"
+    href="https://reportportal.io/case-studies/reducing-regression-time-by-50-percent/"
+  />
+</head>
 
 # Reducing regression time by 50%
 
@@ -29,4 +37,7 @@ EPAM helps a Canadian retail company to reverse-engineer their legacy IBM-based
 - Test Case History helped to identify flaky test cases
 - Extended ML Analyzer
 
-<MediaViewer src={require('./img/CaseStudy1.png')} alt="Case Study Reducing regression time by 50% thanks to our test automation dashboard" />
+<MediaViewer
+  src={require('./img/CaseStudy1.png')}
+  alt="Case Study Reducing regression time by 50% thanks to our test automation dashboard"
+/>
@@ -39,7 +39,7 @@ const config = {
         sitemap: {
           changefreq: 'weekly',
           priority: 0.9,
-          ignorePatterns: ['/docs/search'],
+          ignorePatterns: ['/docs/search', '/docs/search/'],
           filename: 'sitemap.xml',
           createSitemapItems: async (params) => {
             const { defaultCreateSitemapItems, ...rest } = params;

@@ -0,0 +1,3 @@
+import { SearchPageWrapper } from './searchPage';
+
+export default SearchPageWrapper;
@@ -0,0 +1,17 @@
+import React from 'react';
+import Head from '@docusaurus/Head';
+import SearchPage from '@theme-original/SearchPage';
+
+export function SearchPageWrapper(props) {
+  return (
+    <>
+      <Head>
+        <meta name="robots" content="noindex" />
+      </Head>
+      {/* Prop spreading is required here because this is a swizzle wrapper that must
+          forward all props to the original SearchPage component without modification */}
+      {/* eslint-disable-next-line react/jsx-props-no-spreading */}
+      <SearchPage {...props} />
+    </>
+  );
+}
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		import { SearchPageWrapper } from './searchPage';

		export default SearchPageWrapper;