Skip to content
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

Updated the docs as per new UI #290

Merged
merged 2 commits into from
Sep 27, 2023
Merged

Updated the docs as per new UI #290

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
82a9ce7
Updated the docs as per new UI
bharathk08 Sep 27, 2023
6d9a342
Merge branch 'dev' into doc-229
PratheepV Sep 27, 2023
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
84 changes: 29 additions & 55 deletions src/pages/docs/collaboration/users-roles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,83 +20,57 @@ contextual_links:
---

---
When a user is added in Testsigma, they can be assigned various roles. This document covers how to add users and assign them different roles and accesses within Testsigma.

 

---
##**Roles in Testsigma**
Below are the four roles that can be assigned to a project member in Testsigma:

1.**Super Administrator**
A user in a ‘Super Administrator’ role will have complete control over the Testsigma project but will be restricted from viewing Account or Billing-related information.

2.**Test Manager**
A user in the role of ‘Test Manager’ will be able to manage multiple projects - including assigning users to the projects, adding applications, versions in each project.

3.**Test Lead**
A user in the role of ‘Test Lead’ will be able to manage everything in the assigned project - including adding applications, versions in that project.

4.**Automation Engineer/Developer**
A user in the role of ‘Automation Engineer/Developer’ can write, view, update test cases, and everything required to write test cases like test data profiles, Elements, custom functions, etc.

5.**Account Administrator**
A user in the role of ‘Account Administrator’ has all the rights as a Super Administrator. In addition, they will also have access to billing-related information for that particular account.

 
When a user is added in Testsigma, they can be assigned various roles. This document covers how to add users and assign them different roles and accesses within Testsigma.

---
##**Edit Users to Assign New Roles**

1.Go to ‘Settings > Users’, you should see a page like this:

![Users page in Testsigma](https://docs.testsigma.com/images/users-roles/users-page-testsigma.png)

2.Click on the user that you want to edit. You can also search for the user from the search field on the top.
## **Roles in Testsigma**
Below are the four roles that can be assigned to a project member in Testsigma:

3.On the User details page, click on the ‘edit’ button on the top right corner.
1. **Super Administrator:** A user in a ‘Super Administrator’ role will have complete control over the Testsigma project but will be restricted from viewing Account or Billing-related information.

![Edit Button on the User Details page in Testsigma](https://docs.testsigma.com/images/users-roles/edit-button-user-details-page-testsigma.png)
2. **Test Manager:** A user in the role of ‘Test Manager’ will be able to manage multiple projects - including assigning users to the projects, adding applications, versions in each project.

1.A form should appear like the one shown below:
3. **Test Lead:** A user in the role of ‘Test Lead’ will be able to manage everything in the assigned project - including adding applications, versions in that project.

![Update User Details form in Testsigma](https://docs.testsigma.com/images/users-roles/update-user-details-form-testsigma.png)
4. **Automation Engineer/Developer:** A user in the role of ‘Automation Engineer/Developer’ can write, view, update test cases, and everything required to write test cases like test data profiles, Elements, custom functions, etc.

From here, you can fill up the required fields, and change the user role as needed.
5. **Account Administrator:** A user in the role of ‘Account Administrator’ has all the rights as a Super Administrator. In addition, they will also have access to billing-related information for that particular account.

2.Once all the required changes are made, click on the ‘Update’ button

 

---
##**Assign Roles to Users**

1.To assign a project with a particular role to an existing user, refer to [assigning projects](https://testsigma.com/docs/collaboration/assign-projects/)

2.To create a new user and then assign them to one or multiple projects, refer to [Inviting team members](https://testsigma.com/docs/collaboration/invite-team-members/)

## **Edit Users to Assign New Roles**
1. Navigate to **Settings > Users**.
![Settings](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/urmnavsets.png)

 
2. Hover over the user and click on kebab menu.
![Kebab Menu](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/urmkm.png)

### Steps to follow
3. Click on **Edit user role**.
![Edit User](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/nuroleurm.png)

1.Select the project that you want to add users with different roles to.
4. On **Edit User Role / Assign Projects** prompt, select roles and click on **Update**.
![Edit User Roles](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/roleurm.png)

2.Go to Project settings>Project Members

3.Click on the ‘Invite’ button on the top right corner.
---

4.On the ‘Add New Member to Project’ form that opens, add all the required information. You will be able to select the required role from the ‘role’ dropdown field.
## **Assign Roles to Users**
1. Navigate to **Project > Project Settings**, click on **Project members**.
![Project Members](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/urmpmem.png)

![Add New Member to Project form in Testsigma](https://docs.testsigma.com/images/users-roles/add-new-member-to-project-form-testsigma.png)
2. Click on **Invite**.
![Invite](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/urminvite.png)

5.Once all the required fields are filled, click on the ‘Invite’ button on the form.
3. On **Add New Member to Project** prompt, enter **Email** and select the **Role** you want to assign.
![Email & Role](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/urmear.png)

[[info | Note:]]
|This form only allows adding users in ‘Test Manager’, ‘Test Lead’, and ‘Automation Engineer/Developer’ Roles. To read about creating users with Super admin roles, go to the section [“Assign Projects”](https://testsigma.com/docs/collaboration/assign-projects/).
4. Click on **Update**.
![New User](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/urmud.png)

[[info | **NOTE**:]]
| You can only add users as **Test Manager**, **Test Lead**, and **Automation Engineer/Developer**. To assign **Super Admin** roles, refer to [Assign Projects](https://testsigma.com/docs/collaboration/assign-projects/).

The invited user should receive an invitation email. They will need to join via the link sent in the email. Once they have joined they should be able to work on the project according to the role assigned to them.



48 changes: 22 additions & 26 deletions src/pages/docs/integrations/collaboration/slack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "Integrating Slack with Testsigma for test run notifications"
title: "Slack Interation with Testsigma"
metadesc: "Learn how to configure your Slack channel to receive Pass/Fail/Abort notifications about Test Results as in real-time from Testsigma application"
noindex: false
order: 16.21
Expand All @@ -12,49 +12,45 @@ contextual_links:
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Integrating Slack with Testsigma"
url: "#integrating-slack-with-testsigma"
name: "Steps to Integrate Slack with Testsigma"
url: "#steps-to-integrate-slack-with-testsigma"
- type: link
name: "Enabling Slack notifications in Test Plan"
url: "#enabling-slack-notifications-in-test-plan"
---

---

Testsigma Slack integration sends Test **Pass/Fail/Abort** notifications in real-time to your specified Slack channel directly. This ensures that you can collaborate with your teammates by sharing the test results in real-time.
Testsigma Slack integration sends ***Test Pass/Fail/Abort*** notifications in real-time to your specified Slack channel directly. This ensures that you can collaborate with your teammates by sharing the test results in real-time.

---
## **Prerequisites**
We need a Slack Incoming Webhook URL to integrate with Testsigma and we will be using this to post the Test Results to your slack channels.

To know how to generate an Incoming Webhook in Slack, refer to [Sending messages using Incoming Webhooks | Slack](https://api.slack.com/messaging/webhooks)
- Slack Incoming Webhook URL. *For more information, refer to [Incoming Webhooks](https://api.slack.com/messaging/webhooks).*

---
## **Integrating Slack with Testsigma**
Once the Webhook URL is obtained, navigate to the **Plugins page** through **Dashboard > Settings > Plugins** and select **Slack** under the **Collaborations** Tab.
1. Click on the **Disabled Icon**. Slack Details overlay opens up as shown below:
![Add Slack Integration form](https://docs.testsigma.com/images/slack/add-slack-integration-form.png)
2. Enter the details as given below:

a. **Webhook URL:** The incoming webhook URL obtained from Slack.

b. **Post to channel(optional):** Name of the channel if you would like to post to a specific Slack Channel in your organization.

c. **The username that this integration is posted as (optional):** The intended author of the posted message.
## **Steps to Integrate Slack with Testsigma**
1. Navigate to **Settings > Integrations** and enable the toggle on **Slack** widget.
![Integrations](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/navsetslack.png)

After entering the details, click on the **Create button** to add the Integration.
2. On the **Slack details** prompt, enter all the details and click on **Save & Enable**.
![Slack Details](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/sldetailspr.png)

---
## **Enabling Slack notifications in Test Plan**
## **Enabling Slack Notifications in Test Plan**
1. Navigate to **Test Plans > Select/Create a Test Plan > Test Plan Settings**.
![Test Plan Settings](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/tpdslack.png)

Once the slack integration is added, you can enable the **Slack notifications** for your Test Plans while editing any of your existing Test Plans or while creating a new Test Plan.
2. On the **Edit Test Plan** page, enable **Send Notification** toggle.
![Toggle](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/togglesltps.png)

From the **Send Notification When** section on the Test Plan Settings page,
* Under the **On** dropdown, select the Test Plan status for which you want to be notified. You can select multiple statuses from the list.
3. Select the status for which you want to receive the notification.
![Status](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/notonsl.png)

* Under the **send message to** dropdown, select **Slack**.
![Send notification settings under Test Plan Settings ](https://docs.testsigma.com/images/slack/create-edit-test-plan-send-notification-when.png)
4. Select **Slack** from ‘Also send messages to’ dropdown menu.
![Select Slack](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/asmtsl.png)

Here’s what the Notification looks like on Slack:
![Slack notification for Test Results ](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/slack.png)
![Slack](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/slack.png)

Here's a quick GIF demonstrating Slack integration with Testsigma.
![Slack Integration](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/SlackInt.gif)
60 changes: 17 additions & 43 deletions ...s/docs/test-cases/create-steps-recorder/ios-apps/multiple-webview-hybrid-ios.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,62 +1,36 @@
---
title: "Recording tests with webview for hybrid iOS apps"
metadesc: " Recording tests with webview for hybrid iOS apps"
title: "Recording Tests with WebView for Hybrid iOS Apps"
metadesc: "Recording tests with webview for hybrid iOS apps | Learn how to switch the app from NATIVE to HYBRID app view in Testsgima application while recording tests"
noindex: false
order: 4.5394
page_id: "Recording tests with webview for hybrid iOS apps"
warning: false
---
---
<p>While inspecting mobile elements using Testsigma’s <em>Mobile inspector</em>, there are instances where the mobile UI is blank or has no selectable element. In such instances refresh the page again. If the refresh action does not show you the intended mobile UI, the app is a hybrid app that may have some<kbd> WebViews</kbd> which are not being rendered.<p>

<p>In a hybrid app, web components are run completely inside a <kbd>WebView</kbd> control of the application hence we need to switch the context between <kbd>NATIVE</kbd> to <kbd>HYBRID</kbd> to access the elements inside the <kbd>WebView</kbd>. Note that the context is all the relevant information that specifies the current/active state of the application and its interaction with the user. It also specifies how the server interprets commands, and which commands are available to the user. </p>
While inspecting mobile elements using Testsigma's Mobile Inspector, there are instances where the mobile UI is blank or has no selectable element. In such cases, refresh the page again. If the refresh action does not show you the intended mobile UI, the app is a hybrid app that may have some WebViews that are not being rendered.

<p>Currently, Testsigma supports two contexts: <kbd>NATIVE</kbd> and <kbd>HYBRID</kbd>. By default, the mobile app is launched in <kbd>NATIVE</kbd> context.To switch the app from <kbd>NATIVE</kbd> to <kbd>HYBRID</kbd> app view, click <strong>H </strong>from the mobile inspector panel and select <kbd>WebView</kbd> from the drop-down menu.</p>
<img src="https://s3.amazonaws.com/static-docs.testsigma.com/new_images/elements/multiple_web_view/multiple_webview_final.gif" alt="multiple webview">
The below NLP is recorded while switching to <kbd>HYBRID</kbd> app context:<br>
<code>Switch to Webview context</code>
<br><br>
While switching back to <kbd>NATIVE</kbd> context the following NLP is recorded <br>
<code>Switch to Native App Context</code>
In a hybrid app, web components are run completely inside a WebView control of the application. Hence, we need to switch the context between NATIVE and HYBRID to access the elements inside the WebView. Note that the context is all the relevant information that specifies the current/active state of the application and its interaction with the user. It also specifies how the server interprets commands and which commands are available to the user.

Currently, Testsigma supports two contexts: **NATIVE** and **HYBRID**. By default, the mobile app is launched in a NATIVE context. To switch the app from NATIVE to HYBRID app view, click **H** from the mobile inspector panel and select WebView from the drop-down menu.

![WebViews](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/HybridView.gif)

[[info | Note:]]
| The NLP’s are recorded to store user actions of switching views, please do not delete them if you want the execution to continue on the selected <kbd>WebView</kbd>.
The below NLP is recorded while switching to HYBRID app context:

<p>On switching to <kbd>HYBRID</kbd> context the drop-down shows the <kbd>WebViews</kbd> associated with the application.
Here in the below example, there are two types of <kbd> WebView</kbd> contexts <kbd>WebView_TerraceView</kbd> and <kbd>WebView_application</kbd>.
***Switch to Webview context***

<img src="https://s3.amazonaws.com/static-docs.testsigma.com/new_images/elements/multiple_web_view/WebView_Selected.png" alt="webview_selected">
</p>
<p>
On selecting any <kbd>WebView</kbd> the following NLP is added<br>
<kbd>Switch to context with name</kbd><kbd> <em><Name_of_the_webview</em></kbd>
While switching back to NATIVE context the following NLP is recorded

<img src="https://s3.amazonaws.com/static-docs.testsigma.com/new_images/elements/multiple_web_view/Window_handle_before_select.png" alt="window_handle_before_select">
***Switch to Native App Context***

To obtain the list of all the available WebViews as a screenshot use the NLP <br>
<code>Get list of all web views</code>
[[info | **NOTE**:]]
| The NLP’s are recorded to store user actions of switching views, please do not delete them if you want the execution to continue on the selected WebView.

On switching to HYBRID context the drop-down shows the WebViews associated with the application. Here in the below example, there is a webview with the name **WEBVIEW_6890.1**.
![Webview](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/hbawv.png)

Testsigma handles multiple <kbd>WebView</kbd>’s in a single app by treating them as separate windows.
<img src="https://s3.amazonaws.com/static-docs.testsigma.com/new_images/elements/multiple_web_view/Window_Handle_Selected.png" alt="window_handle_selected">
</p>
On selecting the WebView the following NLP is added,

<p>
On selecting any window handle the following NLP is added<br>
<code>Switch to window with index <em>Index_of_window</em></code>

This is because window handle titles can be the same most of the time. Window handle dropdown options will show the <em>index</em> in brackets.
For example,'Simply Travel (0)' . Here 0 is the index.

To set the context to a window with title use the NLP<br>
<code>Switch to window with title test data</code>

To list all window handles, use the NLP <br>
<code>Get list of all window handles</code>



</p>
---
**Switch to context with name *WEBVIEW_6890.1***
![NLP](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/nplhawv.png)
Loading
Loading