Maintaining the Script

Users are empowered with versatile options for managing scripts effectively :

• Edit Script: Users can effortlessly modify script details, including its name, objective and tags, ensuring accurate representation.

• Clone Script: By duplicating existing scripts, users can save time and create variations while retaining the core structure.

• Delete Script: When a script becomes obsolete, users can remove it, maintaining a clean and organized workspace.

• Mark as Component: This feature is to make the Test Scripts built in Web Repository, be reused into Component Service.

• Move Test to Other Module: When reorganizing, users can relocate scripts to different modules, maintaining order and logical grouping.

• Copy Test to Other Module: Users can efficiently duplicate scripts into other modules, enhancing testing efficiency without re-creation.

Editing Script

1. On Modules page click on the "All Repository" Tab.

   
2. Select the module which contains the script to be edited.

3. Select the "Script" which you want to edit.

4. Click on the "Three Dot menu".

   
5. Select "Edit Script" from the dropdown.

6. Edit the desired fields.

7. Click on Update Script .

Cloning Script

1. Select the "Script" which you want to "Clone" .

2. Click on the "Three Dot menu".

3. Select "Clone Script" from the dropdown.

4. The Cloned script will be appended with "_copy"

Deleting Script

1. Select the "Script" which you want to "Delete" .

2. Click on the "Three Dot menu".

3. Select "Delete Script" from the dropdown.

4. Delete Script popup will appear for the confirmation.

   
5. Click on "Delete Script" button to confirm.

6. Once the script is deleted a toast message will be displayed "Script Deleted Successfully" .

Mark as Component

Reusing Test Scripts in Component Service

This feature allows Test Scripts built in the Web Repository to be reused within the Component Service.

1. In the Web Repository, access the "Mark as Component" feature for Test Scripts within a Module.

2. Upon clicking "Mark As Component" , a flag icon will appear.

Note: If a user edits and saves the test scripts again, they need to mark them as a component once more.

1. After marking the Web test scripts as components, they become accessible in the Component Service. Users can import them into their respective projects within the Component Service.

2. Clicking on "Import Scripts" displays the following page, showcasing Web scripts under their respective service.

3. As the user selects the appropriate service, the Test Scripts are presented. Users can choose one or more scripts to import into the component.

4. Clicking the import button opens the screen shown below, allowing users to select the required projects and confirm the import.

   
5. Upon clicking the import button, a success message is displayed.

6. This process ensures the imported test scripts are available in the selected component projects, in draft status.

Users can find shared Test Cases from the Web Repository under the Shared Test module on the workspace page.

Clicking on a shared Test Case reveals the marked-as-component test scripts.

Users can unmark a Shared Test by selecting "Unmark As Component" under the three-dot menu.

Move test to other module

1. Select the "Script" which you want to "Move test to other module" .

2. Click on the "Three Dot menu".

3. Select "Move test to other module" from the dropdown.

4. Select the module to which you want to move the script.

   
5. Click on the "Move to module name" button in the pop up.

   

Copy test to other module

1. Select the "Script" which you want to "Copy test to other module" .

2. Click on the "Three Dot menu".

3. Select "Copy test to other module" from the dropdown.

4. Select the module to which you want to copy the script.

   1. Click on the "Copy to module name" button in the pop up.