Skip to content

Commit 548ba13

Browse files
committed
update images
1 parent fa953ee commit 548ba13

File tree

7 files changed

+8
-8
lines changed

7 files changed

+8
-8
lines changed
-317 KB
Loading
-66 KB
Binary file not shown.
-328 KB
Binary file not shown.
-181 KB
Loading
-209 KB
Loading

docs/create-modules.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Click on the `Create a Module` button. Then, define your module and outline the
6363

6464
Don't worry if you don't have all the details now; you can always edit or add them later.
6565

66-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_creation_page.png').default} alt="automation-dashboard" className="doc_img"/>
66+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_creation_page.png').default} alt="modules-listing-page" className="doc_img"/>
6767

6868
:::note
6969
You must create at least one test step and provide a module name to create a new module.
@@ -76,17 +76,17 @@ Modules support both editing and versioning, but only specific fields trigger a
7676
Only **Test Step** or **Expected Outcome** updation will create a new version of the module.
7777
:::
7878

79-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_page.png').default} alt="automation-dashboard" className="doc_img"/>
79+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_page.png').default} alt="module-page" className="doc_img"/>
8080

8181
## Module Versions
8282

8383
You can easily compare different versions of your module and revert to any previous version. Reverting to a previous version will create a new version in your module's history, ensuring a clear audit trail of all changes.
8484

85-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_version_history.png').default} alt="automation-dashboard" className="doc_img"/>
85+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_version_history.png').default} alt="modules-version-history" className="doc_img"/>
8686

8787
Compare your version history side-by-side to easily identify differences and track changes between various iterations of your module.
8888

89-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_version_comparision.png').default} alt="automation-dashboard" className="doc_img"/>
89+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/modules_version_comparision.png').default} alt="modules-version-comparision" className="doc_img"/>
9090

9191
:::note
9292
Project linking is only added for manual tests in test cases. Hence, modules linked to a particular project are only available to be added in a manual test case. However, for KaneAI test cases, all modules in all projects will be available for selection.

docs/modules-in-manual-testcases.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,11 @@ Here's how to link and manage modules within your manual test cases:
4545

4646
## 1. Module Creation from existing Test Steps
4747
To export test steps as a module, first navigate to the Test Steps page of your desired Test Case. Then, select the **sequential** test steps you wish to include in the module and click the `Create a module` button.
48-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/select_manual_steps_to_create_module.png').default} alt="automation-dashboard" className="doc_img"/>
48+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/select_manual_steps_to_create_module.png').default} alt="select-test-steps" className="doc_img"/>
4949

5050
Clearly define your new module by entering a concise name and a detailed description. This will help you easily identify and understand its purpose later on.
5151

52-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/create_module_from_manual_teststeps.png').default} alt="automation-dashboard" className="doc_img"/>
52+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/create_module_from_manual_teststeps.png').default} alt="create-modules-from-test-steps" className="doc_img"/>
5353

5454
## 2. Import Module into Test Steps
5555

@@ -59,12 +59,12 @@ To incorporate existing modules into your test steps, simply click on the Module
5959
Keep in mind that only modules already linked with your project will be available for import.
6060
:::
6161

62-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/import_module_in_manual_testcases.png').default} alt="automation-dashboard" className="doc_img"/>
62+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/import_module_in_manual_testcases.png').default} alt="import-module" className="doc_img"/>
6363

6464
Notice that imported modules will appear visually distinct from other individual steps within your test case, making them easy to identify. You also have the flexibility to edit or delete these modules directly from this view. However, be aware that making changes will create a new version of that module.
6565

6666
:::note
6767
Please note that when a module is updated to a new version, its existing occurrences within your test cases will not be affected. They will remain linked to the previous version. To utilize the latest version of a module, you'll need to manually sync it by clicking the `Sync to latest` button. This allows you to review and confirm changes before they impact your test cases.
6868
:::
6969

70-
<img loading="lazy" src={require('../assets/images/mobile-app-testing/sync_module_version.png').default} alt="automation-dashboard" className="doc_img"/>
70+
<img loading="lazy" src={require('../assets/images/mobile-app-testing/sync_module_version.png').default} alt="sync-module" className="doc_img"/>

0 commit comments

Comments
 (0)