telerik · plamenmitrev · Jan 7, 2025 · Jan 7, 2025 · Jan 7, 2025 · Jan 8, 2025
diff --git a/.DS_Store b/.DS_Store
diff --git a/.gitignore b/.gitignore
@@ -1 +1,2 @@
-.vscode
+.vscode.DS_Store
+.DS_Store
diff --git a/docs-apitesting/.gitattributes b/docs-apitesting/.gitattributes
diff --git a/docs-apitesting/.gitignore b/docs-apitesting/.gitignore
diff --git a/docs-apitesting/40x.html b/docs-apitesting/40x.html
diff --git a/docs-apitesting/README.md b/docs-apitesting/README.md
diff --git a/docs-apitesting/_config.yml b/docs-apitesting/_config.yml
diff --git a/docs-apitesting/_pdf.yml b/docs-apitesting/_pdf.yml
diff --git a/docs-apitesting/advanced-topics/ci-server-integration.md b/docs-apitesting/advanced-topics/ci-server-integration.md
@@ -4,7 +4,7 @@ page_title: CI Server Integration
 description: "Progress® Test Studio® for APIs - CI Server Integration"
 previous_url: /api-testing/advanced-topics
 position: 1
-publish: true
+published: true
 ---
 
 # CI Server Integration
@@ -14,7 +14,7 @@ Continuous Integration regularly integrates the individual developer's changes i
 Thanks to its command line interface, Test Studio for APIs can easily be integrated in most famous CI Servers.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 ## Jenkins Integration

diff --git a/docs-apitesting/advanced-topics/configure-custom-proxy.md b/docs-apitesting/advanced-topics/configure-custom-proxy.md
@@ -3,7 +3,7 @@ title: Configure Custom Proxy
 page_title: Configure Custom Proxy
 description: "Progress® Test Studio® for APIs - CI Server Integration"
 position: 2
-publish: true
+published: true
 ---
 
 # Overview

diff --git a/docs-apitesting/advanced-topics/http-request-step-authorization.md b/docs-apitesting/advanced-topics/http-request-step-authorization.md
diff --git a/docs-apitesting/copyright.md b/docs-apitesting/copyright.md
diff --git a/docs-apitesting/docs-builder.yml b/docs-apitesting/docs-builder.yml
@@ -0,0 +1,67 @@
+#top nagivation might be wrong
+top-navigation-product: api-testing
+path-prefix: /teststudio-apis/documentation
+product-id: 1720
+product-name: Telerik Test Studio for APIs
+product-url: https://www.telerik.com/teststudio-apis
+search-engine-id: 001595215763381649090:lxlmtcw2g-u
+cta-overview: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+cta-intro: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+default-title-prefix: Telerik Test Studio for APIs
+avatar-path: ./images/avatar-ninja.svg
+no-results-image-path: ./images/ninja-no-results.svg
+primary-color:
+    light: "#1D8800"
+    dark: "#68BF51"
+
+product-code: TESTSTUDIOAPI
+product-trial-url: https://www.telerik.com/try/test-studio-ultimate
+contribute-url: https://github.com/telerik/teststudio-docs/edit/master/docs-apitesting
+enable-tabbed-code-blocks: true
+#pdf-cover-png-path: ./images/pdf-cover.png
+img-max-width: 100%
+table-layout: fixed
+
+
+meta:
+# === Test Studio for APIs Documentation Main Nodes ===
+    getting-started:
+        title: "Getting Started"
+        position: 2
+    features:
+        title: "Features"
+        position: 3
+    advanced-topics:
+        title: "Advanced Topics"
+        position: 4
+    troubleshooting-guide:
+        title: "Troubleshooting Guide"
+        position: 5
+
+#   Features Section        
+    features/steps:
+        title: "Steps"
+        position: 1
+    features/code-features:
+        title: "Code Features"
+        position: 2
+    features/record:
+        title: "Record"
+        position: 3
+    features/command-line:
+        title: "Command Line Interface"
+        position: 4
+
+redirects: 
+-
+    from: "^/?$"
+    to: "/"
+-
+    from: "^/overview$"
+    to: "/"
+-
+    from: "^/features/authorization/basic-authorization$"
+    to: "/features/steps/http-request#authorization"
+-
+    from: "^/features/import/http-traffic$"
+    to: "/features/record/import-http-traffic"
diff --git a/docs-apitesting/downloads/Jenkins_Plugin_Apitesting.zip b/docs-apitesting/downloads/Jenkins_Plugin_Apitesting.zip
diff --git a/docs-apitesting/favicon.ico b/docs-apitesting/favicon.ico
diff --git a/docs-apitesting/features/code-features/add-assembly-reference.md b/docs-apitesting/features/code-features/add-assembly-reference.md
@@ -3,7 +3,7 @@ title: Add Assembly Reference
 page_title: Add Assembly Reference
 description: "Progress® Test Studio® for APIs - Code Features - Add Assembly Reference"
 position: 8
-publish: true
+published: true
 ---
 
 # Add Assembly Reference

diff --git a/docs-apitesting/features/code-features/code-behind-files.md b/docs-apitesting/features/code-features/code-behind-files.md
@@ -3,7 +3,7 @@ title: Code-Behind Files
 page_title: Code-Behind Files
 description: "Progress® Test Studio® for APIs - Code Features - Code-Behind Files"
 position: 2
-publish: true
+published: true
 ---
 
 # Code-Behind Files
@@ -44,7 +44,7 @@ The example below shows hot to log messages to the test output before and after
 
 ![Base Test Methods][4]
 
-```C#
+````C#
 // This method will execute before the start of the test case
 public override void OnBeforeTestStarted()
 {
@@ -56,9 +56,8 @@ public override void OnAfterTestCompleted()
 {
 	this.Log.WriteLine("Ending the test case ...");
 }
-```
-
-```VB
+````
+````VB
 ' This method will execute before the start of the test Case'
 Public Overrides Sub OnBeforeTestStarted()
   Log.WriteLine("The test case is starting ...")
@@ -68,7 +67,7 @@ End Sub
 Public Overrides Sub OnAfterTestCompleted()
   Log.WriteLine("Ending the test case ...")
 End Sub
-```
+````
 
 [Back to top](#Code-Behind-Files)
 
@@ -94,25 +93,24 @@ The **Context.SetValue** method sets a value to a runtime variable. You can stor
 
 #### Examples
 
-```C#
+````C#
 // This statement will create a variable named "user-name" with value "user1"
 // in the scope of the current test case
 this.Context.SetValue("user-name", "user1", o);
 
 // This statement will create a variable named "user-id" with value 123
 // in the root scope of the project
 this.Context.SetValue("user-id", 123, 1);
-```
-
-```VB
+````
+````VB
 // This statement will create a variable named "user-name" with value "user1"
 // in the scope of the current test case
 this.Context.SetValue("user-name", "user1", 0);
 
 // This statement will create a variable named "user-id" with value 123
 // in the root scope of the project
 this.Context.SetValue("user-id", 123, 1);
-```
+````
 
 [Back to top](#Code-Behind-Files)
 
@@ -135,19 +133,18 @@ The **Context.GetValue** method returns the value of a specified runtime variabl
 
 #### Examples
 
-```C#
+````C#
 string userName = this.Context.GetValue("user-name").ToString();
-```
-
-```VB
+````
+````VB
 Dim userName As String = Context.GetValue("user-name").ToString()
-```
+````
 
 > Remember to cast properly your variables when using Context.GetValue. The method returns an object and you need to be aware of where and how the target value was initially created. Any variable, created manually in the Variables pane in the UI, is stored as a string.
 
 ![Casting Variables][5]
 
-```C#
+````C#
 int count = 5;
 this.Context.SetValue("count", count, 0);
 
@@ -164,7 +161,7 @@ this.Log.WriteLine(newUserId.ToString());
 // The "user-name" variable is stored as string, but you still need to convert it with .ToString()
 string userName = this.Context.GetValue("user-name").ToString();
 this.Log.WriteLine(userName);
-```
+````
 
 [Back to top](#Code-Behind-Files)
 
@@ -180,13 +177,12 @@ The **ApiTestBase** base class exposes a **Log** property of type **ILog** which
 
 #### Examples
 
-```C#
+````C#
 this.Log.WriteLine("Logging some message from C# code ...");
-```
-
-```VB
+````
+````VB
 Log.WriteLine("Logging some message from VB code ...")
-```
+````
 
 > See the [Sample Project](../../getting-started/sample-project) for more examples.
 
@@ -198,7 +194,7 @@ The Telerik.ApiTesting.Framework namespace provides a basic assertion framework
 
 The following methods ae available:
 
-```C#
+````C#
 static void AreEqual<T>(T expected, T actual);
 
 static void AreEqual<T>(T expected, T actual, string message);
@@ -226,9 +222,8 @@ static void IsNull(object value, string message);
 static void IsTrue(bool condition);
 
 static void IsTrue(bool condition, string message);
-```
-
-```VB
+````
+````VB
 Shared Sub AreEqual(Of T)(expected As T, actual As T)
 
 Shared Sub AreEqual(Of T)(expected As T, actual As T, message As String)
@@ -256,19 +251,18 @@ Shared Sub IsNull(value As Object, message As String)
 Shared Sub IsTrue(condition As Boolean)
 
 Shared Sub IsTrue(condition As Boolean, message As String)
-```
+````
 
 > When an assertion fails, the execution of the test step will be terminated with status **failed** and the assertion message will be logged to the test output.
 
 ### Examples
 
-```C#
-Assert.AreEqual("administrator", actualValue);
-```
-
-```VB
+````C#
 Assert.AreEqual("administrator", actualValue);
-```
+````
+````VB
+Assert.AreEqual("administrator", actualValue)
+````
 
 ![Assertion Error][6]
 

diff --git a/docs-apitesting/features/code-features/code-items.md b/docs-apitesting/features/code-features/code-items.md
@@ -3,7 +3,7 @@ title: Code Items
 page_title: Code Items
 description: "Progress® Test Studio® for APIs - Code Features - Code Items"
 position: 3
-publish: true
+published: true
 ---
 
 # Code Items

diff --git a/docs-apitesting/features/code-features/coded-steps.md b/docs-apitesting/features/code-features/coded-steps.md
@@ -3,7 +3,7 @@ title: Coded Steps
 page_title: Coded Steps
 description: "Progress® Test Studio® for APIs - Code Features - Coded Steps"
 position: 1
-publish: true
+published: true
 ---
 
 # Coded Steps

diff --git a/docs-apitesting/features/code-features/compile-project.md b/docs-apitesting/features/code-features/compile-project.md
@@ -3,7 +3,7 @@ title: Compile Project
 page_title: Compile Project
 description: "Progress® Test Studio® for APIs - Code Features - Compile Project"
 position: 5
-publish: true
+published: true
 ---
 
 # Compile Project

diff --git a/docs-apitesting/features/code-features/debug-project.md b/docs-apitesting/features/code-features/debug-project.md
@@ -3,7 +3,7 @@ title: Debug Project
 page_title: Compile Project
 description: "Progress® Test Studio® for APIs - Code Features - Debug Project"
 position: 6
-publish: true
+published: true
 ---
 
 # Debug Project
@@ -12,13 +12,12 @@ When a test project is compiled, Progress® Test Studio® for APIs generates a *
 
 To launch the debugger in Visual studio, you can add a `Debugger.Launch()` statement in the code that you wish to debug. (You wll need a `using System.Diagnostics` statement too.)
 
-```C#
-`Debugger.Launch();
-```
-
-```VB
-`Debugger.Launch()`
-```
+````C#
+Debugger.Launch();
+````
+````VB
+Debugger.Launch()
+````
 
 ![Add Debug Statement][1]
 

diff --git a/docs-apitesting/features/code-features/output-panel.md b/docs-apitesting/features/code-features/output-panel.md
@@ -3,7 +3,7 @@ title: Output Panel
 page_title: Output Panel
 description: "Progress® Test Studio® for APIs - Code Features - Output Panel"
 position: 7
-publish: true
+published: true
 ---
 
 # Output Panel

diff --git a/docs-apitesting/features/code-features/overview.md b/docs-apitesting/features/code-features/overview.md
@@ -3,7 +3,7 @@ title: Overview
 page_title: Overview
 description: "Progress® Test Studio® for APIs - Code Features - Overview"
 position: 0
-publish: true
+published: true
 ---
 
 # Code Features Overview

diff --git a/docs-apitesting/features/code-features/project-coding-language.md b/docs-apitesting/features/code-features/project-coding-language.md
@@ -3,7 +3,7 @@ title: Project Coding Language
 page_title: Project Coding Language
 description: "Progress® Test Studio® for APIs - Code Features - Project Coding Language"
 position: 4
-publish: true
+published: true
 ---
 
 # Project Coding Language

diff --git a/docs-apitesting/features/command-line/command-line-parameters.md b/docs-apitesting/features/command-line/command-line-parameters.md
@@ -3,7 +3,7 @@ title: Command Line Parameters
 page_title: Command Line Parameters
 description: "Progress® Test Studio® for APIs - Command Line Parameters"
 position: 1
-publish: true
+published: true
 ---
 # Command Line Parameters
 

diff --git a/docs-apitesting/features/command-line/overview.md b/docs-apitesting/features/command-line/overview.md
@@ -3,14 +3,14 @@ title: Overview
 page_title: Overview
 description: "Progress® Test Studio® for APIs - Command Line Interface - Overview"
 position: 0
-publish: true
+published: true
 ---
 # Command Line Interface - Overview
 
 Test Studio for APIs provides a Command Line Interface application (Telerik.ApiTesting.Runner.exe) that you can use to directly execute an existing test project without using the application's user interface.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 <br>

diff --git a/docs-apitesting/features/condition.md b/docs-apitesting/features/condition.md
@@ -3,7 +3,7 @@ title: Condition
 page_title: Condition
 description: "Progress® Test Studio® for APIs - Condition"
 position: 0
-publish: true
+published: true
 ---
 
 # Condition