Merge pull request #37 from telerik/develop

Merge new KBs; User feedback addressed
telerik · Jan 23, 2024 · 72b3042 · 72b3042
2 parents 20fb9dc + 6168001
commit 72b3042
Show file tree

Hide file tree

Showing 14 changed files with 60 additions and 13 deletions.
diff --git a/docs/features/project-settings/analytics.md b/docs/features/project-settings/analytics.md
@@ -6,8 +6,12 @@ position: 9
 ---
 # Analytics
 
+
+
 Decide whether to allow data collection. Test Studio collect only non-personalized feature usage used for better release planning.
 
 ![Analytics][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 [1]: /img/features/project-settings/analytics/fig1.png
diff --git a/docs/features/project-settings/browsers.md b/docs/features/project-settings/browsers.md
@@ -10,6 +10,8 @@ Under the __Browsers__ tab in _Project Settings_, you can set your preferred bro
 
 ![Browsers][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Preferred Browser
 
 Select an installed and supported browser from the __Preferred Browser__ section to set it as the default test recording and quick execution browser for web tests and <a href="/automated-tests/responsive/responsive-test" target="_blank">responsive web tests</a> (responsive web tests support only Chrome and Edge Chromium).

diff --git a/docs/features/project-settings/element-images.md b/docs/features/project-settings/element-images.md
@@ -10,6 +10,8 @@ Apply specific <a href="/features/elements-explorer/elements-find-expression#ele
 
 ![Element Images][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Recording
 
 - Enable/Disable image recording for elements and set the default threshold value to match the images.

diff --git a/docs/features/project-settings/emulated-device.md b/docs/features/project-settings/emulated-device.md
@@ -10,6 +10,8 @@ Under the Emulated Device Tab, you can set your preferred emulated device displa
 
 ![Emulated Device][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Device
 
 Choose a device type to simulate different device display size. You can choose to manually enter the _Width_ and _Height_ values or select any of the predefined device types.

diff --git a/docs/features/project-settings/find-logic.md b/docs/features/project-settings/find-logic.md
@@ -8,6 +8,8 @@ position: 6
 
 Test Studio uses an intelligent element identification algorithm to auto-generate find expressions for Web and Desktop elements. It is based on the unique element attributes as ordered in the __Smart Find Logic__ list. 
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 Find out more about the Smart Find Logic setting for web and Dekstop elements. 
 
 ## Find Logic for Web Elements 

diff --git a/docs/features/project-settings/general.md b/docs/features/project-settings/general.md
@@ -10,6 +10,8 @@ The General section displays miscellaneous settings for specialized circumstance
 
 ![General][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Enable Storyboard
 
 By default, screenshots are automatically added to the Storyboard Tab. When this option is unchecked, a placeholder image is used. Uncheck the option when you want to conserve memory and disk space. The Scale slider adjusts the size of the Storyboard Tab between "10%" and "100%".

diff --git a/docs/features/project-settings/overview.md b/docs/features/project-settings/overview.md
@@ -6,13 +6,13 @@ position: 0
 ---
 # Test Studio Project Settings
 
-On the *Project* ribbon in Test Studio Standalone version, there is a **Settings** button which displays the Project Settings dialog. In the Visual Studio plugin, the gear icon in the toolbar loads Project Settings.
-
-Use this dialog to configure how tests are recorded, fine tune how web page elements are located, extend Test Studio with new translators, and get information about the current installation. Many of these settings can be quite specialized, so expect to use the defaults as you get started with Test Studio and change the settings as you find need for them.
+Use the **Project Settings** to configure how tests are recorded, fine tune how web page elements are located, extend Test Studio with new translators, and get information about the current installation. We recommend using the default settings as you get started with Test Studio and apply changes when you are sure you need any.
 
 > These settings only apply to tests in the current project. </br>
 > </br>
-> As of release **R3 2019 SP2 (v.2019.3.1405)** Test Studio project settings can be imported to a new project.
+> As of release **R3 2019 SP2 (v.2019.3.1405)** Test Studio project settings can be imported to a new project through the <a href="/features/project-explorer/overview#project-context-menu-options" target="_blank">project context menu options</a>.
+
+On the **Project** ribbon in Test Studio Standalone version find the **Settings** button which opens the Project Settings window. In the Visual Studio plugin, the gear icon in the toolbar loads the same Project Settings window.
 
 <table id="no-table">
 <tr>

diff --git a/docs/features/project-settings/recording-options.md b/docs/features/project-settings/recording-options.md
@@ -10,6 +10,8 @@ Use Recording section to configure how recording will take place. Some of the op
 
 ![Recording Options][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Highlighting
 
 The "Automation Overlay Surface" defines the highlight border color, border width and the amount of time before the Elements Menu displays.<br>

diff --git a/docs/features/project-settings/script-options.md b/docs/features/project-settings/script-options.md
@@ -10,6 +10,8 @@ Script Options dictate how Test Studio treats the <a href="/advanced-topics/code
 
 ![Script Options][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Assembly Name
 
 Defaults to the name of the project.

diff --git a/docs/features/project-settings/theme.md b/docs/features/project-settings/theme.md
@@ -8,6 +8,8 @@ position: 10
 
 The default theme of Test Studio is **Light**. You can change it to **Dark** and back to **Light** at any time. The theme settings are applied after you restart Test Studio.
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 The screenshots below show different views from Test Studio in both themes.
 
 Project theme settings

diff --git a/docs/features/project-settings/translators.md b/docs/features/project-settings/translators.md
@@ -8,6 +8,8 @@ position: 8
 
 The <a href="/getting-started/test-recording/translators" target="_blank">built-in translators</a> are __extensions that open up an element to work with Test Studio__ and thus allow interaction with the Elements Menu exposing a rich set of verification tasks.
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 This section of the <a href="/features/project-settings/overview" target="_blank">Project Settings</a> allows you to __adjust the version of the Telerik and Kendo UI components__ used to build the application under test and lets Test Studio apply the matching translators. From this menu you can review and __disable/enable the components__ for which a translator is available.
 
 ![Translators Project Settings][1]
@@ -745,7 +747,7 @@ In the below grid you can find the versions of the supported UI components match
 
 ## Available Translators
 
-The __Available Translators__ section lists __all built-in translators__ that are currently available in Test Studio. All translators are enabled by default, which is the __recommended setup__. Each of the built-in translators can be disabled and not used while recording and executing tests, but we strongly advise you to contact the Test Studio Support Team prior to applying changes to the enabled translators.
+The __Available Translators__ section lists __all built-in translators__ that are currently available in Test Studio. All translators are enabled by default, which is the __recommended setup__. Each of the built-in translators can be disabled and not used while recording and executing tests, but we strongly recommend contacting the Test Studio Support Team before  applying changes to the enabled translators.
 
 ![Available Translators][3]
 

diff --git a/docs/features/project-settings/updates.md b/docs/features/project-settings/updates.md
@@ -10,6 +10,8 @@ This section in Project Settings lists details for the product version and allow
 
 ![Updates][1]
 
+> Check <a href="/features/project-settings/overview" target="_blank">here how to open the **Project Settings** window</a>. 
+
 ## Product Version
 
 This section displays your currently installed version number.

diff --git a/...est-recording-kb/test-studio-inspecting-context-menu-hidden-behind-app-menus.md b/...est-recording-kb/test-studio-inspecting-context-menu-hidden-behind-app-menus.md
@@ -11,23 +11,25 @@ res_type: kb
 
 ## Description
 
-When working with Test Studio's highlighting quick menu in recording mode on a combobox or context menu in the tested application, you may encounter an issue where the Test Studio menu is hidden behind the app menus. This makes it difficult to interact with the elements using the Test Studio recorder.
+When working with Test Studio's <a href="/automated-tests/recording/hover-over-highlighting" target="_blank">highlighting quick menu in recording mode</a> on a combobox or context menu in the tested application, you may encounter an issue where the Test Studio menu is hidden behind the app menus. This makes it difficult to interact with the elements using the Test Studio recorder.
 
-## Solution
+## Solution 1
 
-To work around this issue, follow these steps:
+To workaround the issue, follow these steps:
 
-1. Start the recording session and record click actions on the combobox or context menu elements directly, instead of using the Test Studio quick menu.
+1. Start the recording session and <a href="/automated-tests/recording/overview#how-to-add-steps-in-the-test" target="_blank">record click actions</a> on the combobox or context menu elements directly, instead of using the Test Studio quick menu.
 2. This will add a step and an element to the test.
-3. Use the recorded element to add steps offline through the Step Builder.
+3. Use the <a href="/features/custom-steps/overview#add-step-for-a-recorded-element" target="_blank">recorded element to add steps offline through the Step Builder</a>.
 4. Once you have the desired steps, you can remove the recorded click step if it is not necessary.
 
+## Solution 2
+
 Alternatively, you can use the DOM explorer in the Advanced Recording tool to work with the combobox or context menu elements. Here's how:
 
-1. Open the Advanced Recording tool during a recording session.
+1. Open the Advanced Recording Tools window from the <a href="/automated-tests/recording/overview#what-is-the-compact-recorder" target="_blank">compact recorder</a>.
 2. Switch to the application and open the combobox or context menu.
-3. Press the 'Scroll Lock' key to freeze the DOM in its current state.
+3. Press the 'Scroll Lock' key to freeze the DOM in its current state. The <a href="/features/recorder/advanced-recording-tools/dom-explorer#toolbar-options" target="_blank">option to freeze the DOM</a> stops the auto-refresh and keeps the DOM as it was at the time of the freeze. 
 4. Switch back to the Advanced Recording window and search for the desired elements in the DOM.
-5. Select the desired element and add steps from the Element steps tab.
+5. Select the element and <a href="/features/recorder/advanced-recording-tools/element-steps/steps-overview" target="_blank">add steps from the Element steps tab</a>.
 
 
diff --git a/...leshooting-guide/test-execution-problems-tg/steps-not-shown-ts-versions-diff.md b/...leshooting-guide/test-execution-problems-tg/steps-not-shown-ts-versions-diff.md
@@ -0,0 +1,21 @@
+---
+title: Test Steps Not Showing in Step Panel
+page_title: Test Steps Not Showing in Step Panel
+description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+position: 1
+---
+# Test Steps Not Showing in Step Panel
+
+
+## Problem
+
+Steps are not shown in the step panel when opening a test from the project explorer. An empty screen appears instead of the recorded steps.
+
+**Reason: The project is opened with Test Studio version which is older than the one used for creating the tests.** 
+
+## Solution
+
+Update the Test Studio installation to the latest available or least to the one used to create the project.
+
+- <a href="/prerequisites/installation/manual-download#download-the-test-studio-installation-file" target="_blank">Download Available Test Studio Versions</a>
+- <a href="/prerequisites/installation/check-for-updates" target="_blank">Update Current Test Studio Version</a>