We can now use data-testid as a
selector attribute. This commit
documents this

These words fail linting because
they should be in backticks

Related epic: https://gitlab.com/groups/gitlab-com/-/epics/1940

Changelog: changed

Updates the e2e docs to use brackets consistently in examples.
Specifically, we use brackets for method calls that aren't for an
internal DSL as per the ruby style guide
https://rubystyle.guide/#method-call-parentheses

Continuing through the docset, fixing more spelling issues as I
find them.

Move the Possessive.yml rule to error status, to satisfy a request
from Legal.

The previous URL had two drawbacks:

1. It didn't match what the title was about (`Assignments to DevOps
   Stages and Groups`, and the anchor was `#designated-technical-writers`).
2. It didn't account for the other sections, like development and API
   guidelines.

These pages used future tense, instead of the present tense, which
is GitLab tone and style. No substantive changes to content were made.

Create a real redirect instead of what was here.

More words that should be allowed to pass through the spell checker.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Sentences should be split by single spaces
only. Fixing in /development and /administration

To eliminate branch pipeline

Switch Issue expectations to use new selection
Add documentation for extensibility

Apply suggestion to app/views/projects/issues/_issue.html.haml

Introduced in 12.5

Refactor k,v/key,value a/attr
Fix docs-lint and static-analysis failures

Update product name capitalization and implement
proper backtick use in /doc/development

Includes API methods to add members to projects and groups

Includes API methods to add members to projects and groups

Adds MD010 (Hard tabs), MD012 (blank lines), MD029 (ordered
list prefix), MD030 (spaces after list markers), and fixes
remaining docs that were failing these tests

The documentation referred to the .act method
This MR changes this to refer to the preferred
.perform method

Documentation was lacking for the [data-qa-selector]
method of defining methods vs .qa-selector method.

Also adds and one linting rule
and makes project conform to it.

First iteration on the documentation for how
dynamic element validation works within the
GitLab QA framework and how to utilize it

Previously the documentation was separated.  If we want to bake
quality into the product, how better than to include everything
we use directly in the development documentation

Signed-off-by: ddavison <ddavison@gitlab.com>

Fix broken internal doc link

Move documentation for page objects to the e2e section

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>

We can infer from the given examples but it is implicit.

We have an explanation for `explain` (by way of examples) but nothing to
say what view does.

In gitlab-org/gitlab-ce!17807 the `package-qa` job was renamed to
`package-and-qa`. But it was not renamed in the docs. So this change
fixes that.