Skip to content

Remove links temporarily #754

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 9, 2020
Merged

Remove links temporarily #754

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4cc0285
Remove links temporarily
tomreece Jul 9, 2020
3211363
Add back links
tomreece Jul 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/backward-incompatible-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ We removed support to read test modules from the deprecated path `dev/tests/acce
- Files under test modules `ActionGroup`, `Page`, `Section`, `Test` and `Suite` only support a single entity per file.
- The `file` attribute from `<module>` has been removed from the suite schema. `<module file=""/>` is no longer supported in suites.
- Metadata filename format changed to ***`*Meta.xml`***.
- Only nested assertion syntax will be supported. See the [assertions page](./docs/test/assertions.md) for details. Here is an example of the nested assertion syntax:
- Only nested assertion syntax will be supported. See the [assertions page](test/assertions.md) for details. Here is an example of the nested assertion syntax:
```xml
<assertEquals stepKey="assertAddressOrderPage">
<actualResult type="const">$billingAddressOrderPage</actualResult>
Expand All @@ -40,7 +40,7 @@ To run the upgrade tests:

1. Run `bin/mftf reset --hard` to remove old generated configurations.
1. Run `bin/mftf build:project` to generate new configurations.
1. Run `bin/mftf upgrade:tests`. [See command page for details](./docs/commands/mftf.md#upgradetests).
1. Run `bin/mftf upgrade:tests`. [See command page for details](commands/mftf.md#upgradetests).
1. Lastly, try to generate all tests. Tests should all be generated as a result of the upgrades. If not, the most likely issue will be a changed XML schema. Check error messaging and search your codebase for the attributes listed.

## MFTF commands
Expand All @@ -57,7 +57,7 @@ To run the upgrade tests:

**Details**:

The `helper` allows test writers to solve advanced requirements beyond what MFTF offers out of the box. See [custom-helpers](./docs/custom-helpers.md) for more information on usage.
The `helper` allows test writers to solve advanced requirements beyond what MFTF offers out of the box. See [custom-helpers](custom-helpers.md) for more information on usage.

Here is an example of using `helper` in place of `executeSelenium` to achieve same workflow.

Expand Down Expand Up @@ -95,7 +95,7 @@ New usage:

**Details**:

See the [actions page for details](./docs/test/actions.md#pause). Here is a usage example:
See the [actions page for details](test/actions.md#pause). Here is a usage example:

```xml
<pause stepKey="pauseExecutionKey"/>
Expand Down