[docs] Fix broken links (DevExpress#4201)

AlexKamaev · Aug 27, 2019 · 3461207 · 3461207
1 parent a17f3e4
commit 3461207
Show file tree

Hide file tree

Showing 8 changed files with 13 additions and 13 deletions.
diff --git a/docs/articles/blog/2017-6-13-testcafe-v0-16-0-released.md b/docs/articles/blog/2017-6-13-testcafe-v0-16-0-released.md
@@ -49,7 +49,7 @@ For details, see [Using Chrome-specific Features](https://devexpress.github.io/t
 
 ### ⚙ Support HTML5 Drag and Drop ([#897](https://github.com/DevExpress/testcafe/issues/897))
 
-Starting with this release, TestCafe supports HTML5 drag and drop, so you can test elements with the `draggable` [attribute](http://w3c.github.io/html/editing.html#the-draggable-attribute).
+Starting with this release, TestCafe supports HTML5 drag and drop, so you can test elements with the `draggable` [attribute](https://html.spec.whatwg.org/multipage/dnd.html#the-draggable-attribute).
 
 ### ⚙ Fixed URL for opening remote browsers ([#1476](https://github.com/DevExpress/testcafe/issues/1476))
 

diff --git a/docs/articles/blog/2018-08-02-testcafe-v0-21-0-released.md b/docs/articles/blog/2018-08-02-testcafe-v0-21-0-released.md
@@ -57,7 +57,7 @@ See [Connect to TestCafe Server over HTTPS](https://devexpress.github.io/testcaf
 
 ### ⚙ Construct Screenshot Paths with Patterns ([#2152](https://github.com/DevExpress/testcafe/issues/2152))
 
-You can now use patterns to construct paths to screenshots. TestCafe provides a number of placeholders you can include in the path, for example, `${DATE}`, `${TIME}`, `${USERAGENT}`, etc. For a complete list, refer to the command line [--screenshot-path-pattern flag description](https://devexpress.github.io/testcafe/documentation/using-testcafe/command-line-interface.html#-p---screenshot-path-pattern).
+You can now use patterns to construct paths to screenshots. TestCafe provides a number of placeholders you can include in the path, for example, `${DATE}`, `${TIME}`, `${USERAGENT}`, etc. For a complete list, refer to the command line [--screenshot-path-pattern flag description](https://devexpress.github.io/testcafe/documentation/using-testcafe/command-line-interface.html#-p-pattern---screenshot-path-pattern-pattern).
 
 You specify a screenshot path pattern when you run tests. Each time TestCafe takes a screenshot, it substitutes the placeholders with actual values and saves the screenshot to the resulting path.
 

diff --git a/docs/articles/blog/2019-2-7-testcafe-v1-0-0-released.md b/docs/articles/blog/2019-2-7-testcafe-v1-0-0-released.md
@@ -17,7 +17,7 @@ TestCafe v1.0.0 introduces minor changes to the framework's behavior and program
 
 ### ⚙ Video Recording ([#2151](https://github.com/DevExpress/testcafe/issues/2151))
 
-You can now [record videos of test runs](https://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/screenshots-and-videos.html#record-videos) in Google Chrome and Mozilla Firefox. To enable video recording, [install the FFmpeg library](https://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/screenshots-and-videos.html#prerequisites) and then do one of the following:
+You can now [record videos of test runs](https://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/screenshots-and-videos.html#record-videos) in Google Chrome and Mozilla Firefox. To enable video recording, [install the FFmpeg library](https://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/screenshots-and-videos.html#prerequisites-for-video-recording) and then do one of the following:
 
 * specify the [--video](https://devexpress.github.io/testcafe/documentation/using-testcafe/command-line-interface.html#--video-basepath) command line flag,
 

diff --git a/docs/articles/documentation/continuous-integration/gitlab.md b/docs/articles/documentation/continuous-integration/gitlab.md
@@ -17,7 +17,7 @@ However, if you already have a Docker image prepared to deploy your web applicat
 
 Open the `.gitlab-ci.yml` file that stores the GitLab CI configuration. If this file does not exist, create it in the repository's root directory.
 
-Create a new [job](https://docs.gitlab.com/ee/ci/pipelines.html#jobs). To do this, add the following settings to `.gitlab-ci.yml` at the top level:
+Create a new [job](https://docs.gitlab.com/ee/ci/pipelines.html). To do this, add the following settings to `.gitlab-ci.yml` at the top level:
 
 ```yaml
 e2e_tests:
@@ -36,7 +36,7 @@ e2e_tests:
 
 See [Configuration of your jobs with .gitlab-ci.yml](https://docs.gitlab.com/ee/ci/yaml/README.html) for more information about the `.gitlab-ci.yml` syntax.
 
-Commit `.gitlab-ci.yml` and push the changes to the repository. This creates a new [job](https://docs.gitlab.com/ee/ci/pipelines.html#jobs) that any [GitLab Runner](https://docs.gitlab.com/ee/ci/runners/README.html) can execute.
+Commit `.gitlab-ci.yml` and push the changes to the repository. This creates a new job that any [GitLab Runner](https://docs.gitlab.com/ee/ci/runners/README.html) can execute.
 
 ## Option 2 - Install TestCafe on a Docker Image
 
@@ -74,7 +74,7 @@ The test run command that uses TestCafe should be also added to `package.json` t
 
 This allows you to use `npm test` to run tests.
 
-Finally, open `.gitlab-ci.yml` (or create it in the repository root) and add a [job](https://docs.gitlab.com/ee/ci/pipelines.html#jobs) that installs TestCafe and runs tests.
+Finally, open `.gitlab-ci.yml` (or create it in the repository root) and add a job that installs TestCafe and runs tests.
 
 ```yaml
 e2e_tests:

diff --git a/docs/articles/documentation/recipes/extract-reusable-test-code/use-page-model.md b/docs/articles/documentation/recipes/extract-reusable-test-code/use-page-model.md
@@ -86,7 +86,7 @@ This class will contain the Page Model, so name the file `page-model.js`.
 ### Step 2 - Add a Page Element to the Page Model
 
 Add the `Developer Name` input element to the model. To do this,
-introduce the `nameInput` property and assign a [selector](../test-api/selecting-page-elements/selectors/README.md) to it.
+introduce the `nameInput` property and assign a [selector](../../test-api/selecting-page-elements/selectors/README.md) to it.
 
 ```js
 import { Selector } from 'testcafe';
@@ -211,7 +211,7 @@ test('Click check boxes and then verify their state', async t => {
 
 Add an action that enters the developer name and clicks the Submit button.
 
-1. Import `t`, a [test controller](../test-api/test-code-structure.md#test-controller), from the `testcafe` module.
+1. Import `t`, a [test controller](../../test-api/test-code-structure.md#test-controller), from the `testcafe` module.
 
     ```js
     import { Selector, t } from 'testcafe';

diff --git a/docs/articles/documentation/recipes/use-angular-cli-builder.md b/docs/articles/documentation/recipes/use-angular-cli-builder.md
@@ -19,7 +19,7 @@ npm install --save-dev @politie/angular-testcafe-builder
 
 ## Configure a Target in the Angular Workspace
 
-Open `angular.json` and configure the `e2e` [Architect target](https://angular.io/guide/workspace-config#project-tool-configuration-options) to run TestCafe tests.
+Open `angular.json` and configure the `e2e` *Architect target* to run TestCafe tests.
 
 To do this, specify the `@politie/angular-testcafe-builder:testcafe` command in the `builder` property and provide TestCafe arguments in the `options` property:
 

diff --git a/docs/articles/documentation/using-testcafe/programming-interface/runner.md b/docs/articles/documentation/using-testcafe/programming-interface/runner.md
@@ -422,11 +422,11 @@ async clientScripts( script[, script2[, ...[, scriptN]]] ) → this
 
 Parameter | Type                | Description
 --------- | ------------------- | ------------
-`script`, `script2`, `scriptN`  | String &#124; Object &#124; Array | Scripts to inject into the tested pages. See [Provide Scripts to Inject](common-concepts/inject-scripts-into-tested-pages.md#provide-scripts-to-inject) to learn how to specify them.
+`script`, `script2`, `scriptN`  | String &#124; Object &#124; Array | Scripts to inject into the tested pages. See [Provide Scripts to Inject](../common-concepts/inject-scripts-into-tested-pages.md#provide-scripts-to-inject) to learn how to specify them.
 
 > Relative paths resolve from the current working directory.
 
-You can use the [page](common-concepts/inject-scripts-into-tested-pages.md#provide-scripts-for-specific-pages) option to specify pages into which scripts should be injected. Otherwise, TestCafe injects scripts into all pages visited during the test run.
+You can use the [page](../common-concepts/inject-scripts-into-tested-pages.md#provide-scripts-for-specific-pages) option to specify pages into which scripts should be injected. Otherwise, TestCafe injects scripts into all pages visited during the test run.
 
 ```js
 runner.clientScripts('assets/jquery.js');
@@ -446,7 +446,7 @@ runner.clientScripts([
 
 The [fixture.clientScripts](../../test-api/test-code-structure.md#inject-scripts-into-tested-pages) and [test.clientScripts](../../test-api/test-code-structure.md#inject-scripts-into-tested-pages) methods allow you to inject scripts into pages visited during an individual fixture or test.
 
-See [Inject Scripts into Tested Pages](common-concepts/inject-scripts-into-tested-pages.md) for more information.
+See [Inject Scripts into Tested Pages](../common-concepts/inject-scripts-into-tested-pages.md) for more information.
 
 *Related configuration file property*: [clientScripts](../configuration-file.md#clientscripts)
 

diff --git a/docs/articles/faq/README.md b/docs/articles/faq/README.md
@@ -55,7 +55,7 @@ The table below compares TestCafe and TestCafe Studio:
 | Free and open-source | &#10003; | &nbsp; |
 | [Visual Test Recorder](https://docs.devexpress.com/TestCafeStudio/400165/guides/record-tests) | &nbsp; | &#10003; |
 | [Interactive Test Editor](https://docs.devexpress.com/TestCafeStudio/400190/user-interface/test-editor) | &nbsp; | &#10003; |
-| [Automatic Selector Generation](https://docs.devexpress.com/TestCafeStudio/400407/guides/record-tests/element-selectors#auto-generated-element-selectors) | &nbsp; | &#10003; |
+| [Automatic Selector Generation](https://docs.devexpress.com/TestCafeStudio/400407/test-actions/element-selectors#auto-generated-element-selectors) | &nbsp; | &#10003; |
 | [Run Configuration Manager](https://docs.devexpress.com/TestCafeStudio/400189/user-interface/run-configurations-dialog) | &nbsp; | &#10003; |
 | [IDE-like GUI](https://docs.devexpress.com/TestCafeStudio/400181/user-interface/code-editor) | &nbsp; | &#10003; |