Skip to content

Commit 0698d92

Browse files
committed
Updated images to markdown.
1 parent 7f0207a commit 0698d92

File tree

7 files changed

+11
-10
lines changed

7 files changed

+11
-10
lines changed

docs/data.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
The MFTF enables you to specify and use `<data>` entities defined in XML. Default `<data>` entities are provided for use and as templates for entity creation and manipulation.
66
The following diagram shows the XML structure of an MFTF data object:
77

8-
<img src="img/data-dia.svg" />
8+
![MFTF Data Object](img/data-dia.svg)
99

1010
## Supply data to test by reference to a data entity
1111

docs/metadata.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ When a test step requires handling the specified data entity, the MFTF performs
3939
- Stores a response and provides access to its data using MFTF variables syntax in XML.
4040

4141
The following diagram demonstrates the XML structure of a metadata file:
42-
<img src="img/metadata-dia.svg" />
42+
![Structure of metadata](img/metadata-dia.svg)
4343

4444
## Format {#format}
4545

docs/page.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Two types of pages are available:
1919

2020
The following diagram shows the XML structure of an MFTF page:
2121

22-
<img src="img/page-dia.svg" />
22+
![XML Structure of MFTF Page](img/page-dia.svg)
2323

2424
## Format
2525

docs/section.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Substitutable values in the test can be of the following formats:
2121

2222
The following diagram shows the XML structure of an MFTF section:
2323

24-
<img src="img/section-dia.svg%" />
24+
![XML Structure of MFTF section](img/section-dia.svg)
2525

2626
## Format
2727

docs/test.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The steps in `<after>` are run in both successful **and** failed test runs.
1414

1515
The following diagram shows the structure of an MFTF test case:
1616

17-
<img src="img/test-dia.svg"/>
17+
![Structure of MFTF test case](img/test-dia.svg)
1818

1919
## Format
2020

docs/test/action-groups.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,10 @@
11
# Action groups
22

3-
<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
4-
53
In the MFTF, you can re-use a group of [actions][], such as logging in as an administrator or a customer, declared in an XML file when you need to perform the same sequence of actions multiple times.
64

75
The following diagram shows the structure of an MFTF action group:
86

9-
<img src="../img/action-groups-dia.svg" />
7+
![Structure of MFTF action group](../img/action-groups-dia.svg)
108

119
## Principles
1210

docs/tips-tricks.md

+5-2
Original file line numberDiff line numberDiff line change
@@ -331,7 +331,7 @@ When possible, select the first parent tag and then specify the desired element
331331

332332
**Why?** Elements that are overly specific are less flexible and may fail if unexpected DOM changes occur. It also reduces the amount of the DOM it needs to parse.
333333

334-
<span stype="color:green">
334+
<span style="color:green">
335335
GOOD:
336336
</span>
337337

@@ -383,6 +383,8 @@ When working with input type `checkbox`, do not use the `click` action; use `che
383383
GOOD:
384384
</span>
385385

386+
<!--{% raw %}-->
387+
386388
```xml
387389
<checkOption selector="{{ProductInWebsitesSection.website('Second Website')}}" stepKey="selectSecondWebsite"/>
388390
<uncheckOption selector="{{ProductInWebsitesSection.website('Second Website')}}" stepKey="unselectSecondWebsite"/>
@@ -395,4 +397,5 @@ BAD:
395397
```xml
396398
<click selector="{{ProductInWebsitesSection.website('Second Website')}}" stepKey="selectSecondWebsite"/>
397399
<click selector="{{ProductInWebsitesSection.website('Second Website')}}" stepKey="unselectSecondWebsite"/>
398-
```
400+
```
401+
<!--{% endraw %}-->

0 commit comments

Comments
 (0)