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.

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

Created a new doc for Prerequisites for Cloud Executions #344

Merged
merged 1 commit into from
Jan 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
57 changes: 57 additions & 0 deletions src/pages/docs/getting-started/prerequisites-cloud.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
---
title: "Prerequisites for Cloud Executions"
metadesc: "In Testsigma, some prerequisites are necessary to avoid issues and enhance the flexibility. This article discusses prerequisites for cloud executions"
noindex: false
order: 1.9
page_id: "Testsigma Sample Apps"
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
name: "Important Prerequisites for Cloud Executions"
url: "#important-prerequisites-for-cloud-executions"
---

---

For cloud executions, some prerequisites are necessary to avoid issues and enhance the flexibility, security, and efficiency of the testing. This article discusses recommendations and requirements for smooth cloud executions in Testsigma.

---

## **Important Prerequisites for Cloud Executions**

**1. IP Whitelisting**: When the application is hosted on servers with restricted access from unknown sources, you can use Testsigma Labs to execute tests by whitelisting Testsigma IP Addresses on your server.
For more information, refer to access locally hosted applications.

- For more information, refer to [access locally hosted applications](https://testsigma.com/docs/runs/test-locally-hosted-applications/).

**2. Agent for Local Executions**: To run the tests locally, you need Testsigma Agent running on the machine for test orchestration, i.e., queueing tests, running the tests, fetching the test results, etc.

For more information, refer to:
- [Testsigma Agent](https://testsigma.com/docs/agent/overview/)
- [Setting up Testsigma Agent (Mac, Windows & Linux)](https://testsigma.com/docs/agent/setup-on-windows-mac-linux/).
- [Setting up Android Local Devices](https://testsigma.com/docs/agent/connect-android-local-devices/)
- [Setting up iOS Local Devices](https://testsigma.com/docs/agent/connect-ios-local-devices/)


**3. iOS App Resigning**: You have to set the ResignEnabled desired capability to true to trigger a process where Testsigma resigns the iOS application with a provisioning profile. This is important to ensure the iOS app can be installed and run on the testing device.
- For more information, refer to [enabling app resigning in iOS](https://testsigma.com/docs/desired-capabilities/app-resigning/).
- For more information on desired capabilities, refer to [most common desire capabilities](https://testsigma.com/docs/desired-capabilities/most-common/).

**4. Testsigma Chrome Extension**: You can quickly record test steps by interacting with the UI, such as clicking buttons, entering text, navigating through pages, etc. To access this feature, you should have the Testsigma Chrome extension.
For more information, refer to:
- [Testsigma Chrome Extension](https://testsigma.com/docs/test-step-recorder/install-chrome-extension/)
- [Create Tests Using Recorder](https://testsigma.com/docs/test-cases/create-test-steps/overview/#creating-test-steps-using-test-recorder)


**5. Addons (To access NLPs)**: Installing Testsigma addons will extend built-in actions with custom actions. These actions can be anything from clicking first, then scrolling, clicking again, scrolling indefinitely till the bottom of the page, and so on.
- For more information, refer to [addons](https://testsigma.com/docs/addons/what-is-an-addon/).


**6. VPN Tunneling**: For security reasons, sometimes the recorder cannot access the application while testing Android and iOS apps. In this case, VPN tunneling can be used to establish a secure and encrypted connection over the internet. You can connect with Testsigma support (*[email protected]*) to know more.




---
8 changes: 6 additions & 2 deletions src/pages/docs/integrations/test-labs/browserstack.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,11 @@ contextual_links:

---

BrowserStack integration with Testsigma lets you run your Testsigma tests on BrowserStack.
[BrowserStack Integration](https://www.browserstack.com/automate?utm_source=testsigma&utm_medium=partnered) with Testsigma lets you run your Testsigma tests on BrowserStack.
If your organization has an existing account with BrowserStack, you can author tests for Web, Mobile Web, and Mobile applications on Testsigma, and then run those tests on BrowserStack’s cloud devices.

---

## **Prerequisites**

You need the username and API Key for BrowserStack which can be obtained from your BrowserStack account dashboard.
Expand All @@ -36,20 +37,23 @@ This can be obtained from the Account Settings page under Automate as shown belo
You should already know about different [Test Lab Types in Testsigma](https://testsigma.com/docs/test-management/test-plans/supported-test-lab-types/)

---

## **Integrating with BrowserStack**

Once the username and API key is obtained, navigate to the Plugins page through **Dashboard > Settings > Plugins** and select BrowserStack under the Test Lab tab.

1. Click on the disabled Icon on BrowserStack. BrowserStack Details overlay opens up.
1. Click on the disabled icon on BrowserStack. BrowserStack Details overlay opens up.
2. Enter the username and API Key obtained from BrowserStack here.

After entering the details, click on the Create button to add the Integration.

---

## **Using BrowserStack for Test Runs**

Once the account details are added to the Plugins page, select BrowserStack as the Test Lab type instead of Testsigma Lab while creating an Ad-hoc run or Test Plan Run.

![Select BrowserStack as the Test lab Type for Test Plan Run or Ad-hoc Run GIF](https://docs.testsigma.com/images/browserstack/select-test-lab-browserstack-gif.png)


---
Loading