diff --git a/docs/advanced-tunnel-features.md b/docs/advanced-tunnel-features.md index 99a8e27bf..62f624e86 100644 --- a/docs/advanced-tunnel-features.md +++ b/docs/advanced-tunnel-features.md @@ -118,7 +118,7 @@ Key: 123456789abcdefghijklmnopqrstuv TunnelName: LambdaTest ``` -> **Note:** You will need to replace this file with your credentials and it has to be named exactly “`.lt.yaml`“. Once you specify the proxy information as environment variable, it gets auto detected. +> **Note:** You will need to replace this file with your credentials and it has to be named exactly "`.lt.yaml`". Once you specify the proxy information as environment variable, it gets auto detected. Similarly, you can go ahead and pass any other variables by just specifying them in the YAML file. For example, if you wish to have verbose variable passed on for detailed logs while the binary is being configured. You will add the verbose flag in your YAML file: diff --git a/docs/app-center-integration.md b/docs/app-center-integration.md index 04ac948e6..2d69880a1 100644 --- a/docs/app-center-integration.md +++ b/docs/app-center-integration.md @@ -82,13 +82,13 @@ Before getting started with the setup, you would need access to the following: *** -2. Click on the “User API Tokens” to generate a token. +2. Click on the "User API Tokens" to generate a token. cmd *** -3. Click on “Add new API token” to add the new token. +3. Click on "Add new API token" to add the new token. cmd @@ -104,7 +104,7 @@ Before getting started with the setup, you would need access to the following: --- -1. Click on the “Configure” Button +1. Click on the "Configure" Button cmd @@ -116,7 +116,7 @@ Before getting started with the setup, you would need access to the following: *** -3. Now Select your Builds on App Center by clicking on “Select Builds” to Select the “Builds” from App Center. +3. Now Select your Builds on App Center by clicking on "Select Builds" to Select the "Builds" from App Center. cmd diff --git a/docs/appium-app-performance.md b/docs/appium-app-performance.md index 245627e0f..ee3a3847f 100644 --- a/docs/appium-app-performance.md +++ b/docs/appium-app-performance.md @@ -52,7 +52,7 @@ LambdaTest provides you with two metrics in a time-series format representing th 1. **System CPU Usage (%)**: The total percentage of CPU being used by the entire system -2. **App CPU Usage (%)**: The share of “System CPU usage” being used by the AUT. +2. **App CPU Usage (%)**: The share of "System CPU usage" being used by the AUT. *** diff --git a/docs/appium-appletv.md b/docs/appium-appletv.md index 4b8e75309..fda645c47 100644 --- a/docs/appium-appletv.md +++ b/docs/appium-appletv.md @@ -253,13 +253,13 @@ if __name__ == "__main__": You can update your custom capabilities in test scripts. In this sample project, we are passing platform name, platform version, device name and app url (generated earlier) along with other capabilities like build name and test name via capabilities object. The capabilities object in the sample code are defined as: **Supported Model:** -- Device: `"Apple TV"` ; OS Version:`“16"` +- Device: `"Apple TV"` ; OS Version:`"16"` **Supported Capabilities:** Same as iOS **Platform:** -`”tvOS"` +`"tvOS"` ```python title="appletv.py" def getCaps(): diff --git a/docs/appium-firetv.md b/docs/appium-firetv.md index c0287100c..964e868c7 100644 --- a/docs/appium-firetv.md +++ b/docs/appium-firetv.md @@ -231,13 +231,13 @@ if __name__ == "__main__": You can update your custom capabilities in test scripts. In this sample project, we are passing platform name, platform version, device name and app url (generated earlier) along with other capabilities like build name and test name via capabilities object. The capabilities object in the sample code are defined as: **Supported Model:** -- Device: `"Amazon Fire TV Stick"` ; OS Version:`“7"` +- Device: `"Amazon Fire TV Stick"` ; OS Version:`"7"` **Supported Capabilities:** Same as Android. **Platform:** -`”fireos"` +`"fireos"` ```python title="firetv.py" def getCaps(): diff --git a/docs/appium-ios-app-settings.md b/docs/appium-ios-app-settings.md index 8fc3679d7..935380e48 100644 --- a/docs/appium-ios-app-settings.md +++ b/docs/appium-ios-app-settings.md @@ -90,7 +90,7 @@ Currently, App Automate supports the following permission settings: One important thing to remember while handling Permission Settings is that, we have to first take action on the **Permission Pop ups** from the app when they appear and then only those particular Permission Settings will be reflected in the app settings page. For example: -Let's say we pass Camera: “On“ in the lambda hook’s preferences even before handling Camera’s permission popup from the app, the Camera key would be missing on the app settings page which would result in failure. So we have to be sure that we have handled the permission pop ups before calling lambda hook. +Let's say we pass Camera: "On" in the lambda hook’s preferences even before handling Camera’s permission popup from the app, the Camera key would be missing on the app settings page which would result in failure. So we have to be sure that we have handled the permission pop ups before calling lambda hook. :::info @@ -122,7 +122,7 @@ Currently, App Automate supports the following custom settings: Apart from Textfields and Sliders, for every other settings, we have to pass the Name of that particular setting as the **key-value pair**. For example: -- “Reset App“ : “On“. +- "Reset App" : "On". For **textfields and sliders**, we pass the index of that particular textfield or slider starting from 1 when we traverse from top to bottom. For example: diff --git a/docs/appium-rokutv.md b/docs/appium-rokutv.md index b559e9e1a..2c39c9973 100644 --- a/docs/appium-rokutv.md +++ b/docs/appium-rokutv.md @@ -226,14 +226,14 @@ if __name__ == "__main__": You can update your custom capabilities in test scripts. In this sample project, we are passing platform name, platform version, device name and app url (generated earlier) along with other capabilities like build name and test name via capabilities object. The capabilities object in the sample code are defined as: **Supported Model:** -- Device: `"Roku Ultra"` ; OS Version:`“11"` -- Device: `"Roku Express"` ; OS Version:`“11"` +- Device: `"Roku Ultra"` ; OS Version:`"11"` +- Device: `"Roku Express"` ; OS Version:`"11"` **Supported Capabilities:** Please check at the end of the doc. **Platform:** -`”roku"` +`"roku"` ```python title="main.py" caps = { diff --git a/docs/appveyor-ci-integration.md b/docs/appveyor-ci-integration.md index 333c1d5d1..292434ef5 100644 --- a/docs/appveyor-ci-integration.md +++ b/docs/appveyor-ci-integration.md @@ -59,7 +59,7 @@ To perform your tests with LambdaTest, you would need the below things to be alr 2. You also need your LambdaTest authentication credentials, which include your LambdaTest username, and access key. -> To get your Username and Access Key, go to your [LambdaTest automation dashboard](https://automation.lambdatest.com/) and click on the “key” icon left to the help button, on the top right corner. appveyor ci integration +> To get your Username and Access Key, go to your [LambdaTest automation dashboard](https://automation.lambdatest.com/) and click on the "key" icon left to the help button, on the top right corner. appveyor ci integration Update your username and access key in the "Config.properties" file. @@ -90,9 +90,9 @@ Below is the step-by-step execution of the AppVeyor CI pipeline. 1. Make sure to add your LambdaTest's hub URL and [Desired Capabilities](/docs/selenium-automation-capabilities/) in your test setup, as done in the _AppveyorCI/src/main/java/stepDefinitions/ToDoStepDefinition.java_ file of the mentioned GitHub repository. 2. Push the changes to your integrated GitHub repository. For example, we have changed the test name in the forked repository. -3. Once the edit is complete, click on “Commit Changes” to save and commit the changes made. AppVeyor CI is activated as soon as this step is done since we have used “push event” for triggering the AppVeyor CI. appveyor ci integration +3. Once the edit is complete, click on "Commit Changes" to save and commit the changes made. AppVeyor CI is activated as soon as this step is done since we have used "push event" for triggering the AppVeyor CI. appveyor ci integration -4. As soon as the AppVeyor CI is triggered (through push event in this case), a new build can be seen in the “Timeline” on your [LambdaTest's automation dashboard](https://automation.lambdatest.com/timeline/). The current status of this build will be “running” or “executing”. appveyor ci integration +4. As soon as the AppVeyor CI is triggered (through push event in this case), a new build can be seen in the "Timeline" on your [LambdaTest's automation dashboard](https://automation.lambdatest.com/timeline/). The current status of this build will be "running" or "executing". appveyor ci integration 5. Now based on the tests, this build can pass or fail. If passed, a green tick along with the term **Passed** will appear in the summary of the test. Else if failed, a red cross will appear instead, along with the term **Failed**, as shown below.appveyor ci integration diff --git a/docs/automation-testing-using-jasmine-with-karma.md b/docs/automation-testing-using-jasmine-with-karma.md index d367c25f3..fb631acd8 100644 --- a/docs/automation-testing-using-jasmine-with-karma.md +++ b/docs/automation-testing-using-jasmine-with-karma.md @@ -186,7 +186,7 @@ customLaunchers: { chrome: { tunnel: true, // In case karma is running on local machine } } ``` -> **Important Note**: Some Safari & IE browsers don’t support automatic resolution of the URL string “localhost”. Therefore if you test on URLs like "`http://localhost/`" or "`http://localhost:8080`" etc, you would get an error in these browsers. A possible solution is to use "`localhost.lambdatest.com`" or replace the string “localhost” with machine IP address. For example, if you wanted to test "`http://localhost/dashboard`" or, and your machine IP is 192.168.2.6 you can instead test on "`http://192.168.2.6/dashboard`" or "`http://localhost.lambdatest.com/dashboard`". +> **Important Note**: Some Safari & IE browsers don’t support automatic resolution of the URL string "localhost". Therefore if you test on URLs like "`http://localhost/`" or "`http://localhost:8080`" etc, you would get an error in these browsers. A possible solution is to use "`localhost.lambdatest.com`" or replace the string "localhost" with machine IP address. For example, if you wanted to test "`http://localhost/dashboard`" or, and your machine IP is 192.168.2.6 you can instead test on "`http://192.168.2.6/dashboard`" or "`http://localhost.lambdatest.com/dashboard`". ## Avoid Timeouts With psuedoActivityInternal * * * diff --git a/docs/aws-codepipeline-with-hyperexecute.md b/docs/aws-codepipeline-with-hyperexecute.md index d35008fba..d29ab4b3b 100644 --- a/docs/aws-codepipeline-with-hyperexecute.md +++ b/docs/aws-codepipeline-with-hyperexecute.md @@ -111,11 +111,11 @@ phases: command: ./hyperexecute --user --key --config ``` -- In the **buildspec** specification, choose the first option - **“Use a buildspec file”**. +- In the **buildspec** specification, choose the first option - **"Use a buildspec file"**. -- Now Click the **“continue to code pipeline”** button and then click on **Next**. +- Now Click the **"continue to code pipeline"** button and then click on **Next**. -- You can “**Skip deploy stage”** and finally click **“Create Pipeline”** button. +- You can "**Skip deploy stage"** and finally click **"Create Pipeline"** button. Image diff --git a/docs/axosoft-integration.md b/docs/axosoft-integration.md index 5e0a669bc..b24728761 100644 --- a/docs/axosoft-integration.md +++ b/docs/axosoft-integration.md @@ -67,7 +67,7 @@ Axosoft Integration with LambdaTest, like all of the integrations to 3rd party a **Step 1:** Log in to your [LambdaTest account](https://accounts.lambdatest.com/register). You need to have Admin or User level access to see and install 3rd party integrations. -**Step 2:** Select the ‘Integrations’ tab from the left navigation menu bar under “Settings”. This will guide you to a screen where you will find a list of 3rd party applications, that have already been integrated as well as that are available to integrate with your LambdaTest account. +**Step 2:** Select the ‘Integrations’ tab from the left navigation menu bar under "Settings". This will guide you to a screen where you will find a list of 3rd party applications, that have already been integrated as well as that are available to integrate with your LambdaTest account. add @@ -91,7 +91,7 @@ Axosoft Integration with LambdaTest, like all of the integrations to 3rd party a add -**Step 8:** Click on the Manage Tokens section, and create a non-expiring token for the app you've just created. Select “LambdaTest” under app, "read and write" under scope, and enter create. +**Step 8:** Click on the Manage Tokens section, and create a non-expiring token for the app you've just created. Select "LambdaTest" under app, "read and write" under scope, and enter create. add @@ -99,7 +99,7 @@ Axosoft Integration with LambdaTest, like all of the integrations to 3rd party a add -**Step 10:** Once you enter “install” Axosoft will be integrated with LambdaTest, and an alert box will appear on the top right corner of the screen stating that the integration is in progress, you will be notified on your mail post successful integration. +**Step 10:** Once you enter "install" Axosoft will be integrated with LambdaTest, and an alert box will appear on the top right corner of the screen stating that the integration is in progress, you will be notified on your mail post successful integration. add @@ -115,7 +115,7 @@ Axosoft Integration with LambdaTest, like all of the integrations to 3rd party a **Step 1:** Select any of the tests from the left navigation menu of LambdaTest. For this instance, we will be taking the "Real Time Testing" option. -**Step 2:** Enter the URL of the web app to be tested in the URL box, and select “mobile” device for testing. Press 'Start' after selecting the configuration of the browser and operating system as per your choice. +**Step 2:** Enter the URL of the web app to be tested in the URL box, and select "mobile" device for testing. Press 'Start' after selecting the configuration of the browser and operating system as per your choice. add @@ -123,7 +123,7 @@ Axosoft Integration with LambdaTest, like all of the integrations to 3rd party a add -**Step 4:** A screenshot will be captured and appear on your screen in an in-built image editor. Annotate any issue as per your choice in this editor, and then press the "Mark as Bug" button under “Axosoft” integration. +**Step 4:** A screenshot will be captured and appear on your screen in an in-built image editor. Annotate any issue as per your choice in this editor, and then press the "Mark as Bug" button under "Axosoft" integration. add @@ -147,7 +147,7 @@ You can work with one integration at a time. So if you want to integrate into a **Step 1:** Log in to your LambdaTest account. -**Step 2:** Select ‘Integrations’ from the left navigation menu bar. This will guide you to a screen where you can remove the Axosoft integration under the tab that says “My Integrations”. +**Step 2:** Select ‘Integrations’ from the left navigation menu bar. This will guide you to a screen where you can remove the Axosoft integration under the tab that says "My Integrations". **Step 3:** On the Axosoft block, a "REMOVE" button will appear. Click on ‘REMOVE’. diff --git a/docs/backlog-integration.md b/docs/backlog-integration.md index 2b15f2325..41d65ec74 100644 --- a/docs/backlog-integration.md +++ b/docs/backlog-integration.md @@ -71,7 +71,7 @@ LambdaTest integration with Backlog will help you file any UI bug on your Backlo Backlog Integration -**Step 6:** On top-right corner of your Backlog instance, you will find a drop-down menu with your profile icon. Click on the drop-down and go to “Personal Settings”. +**Step 6:** On top-right corner of your Backlog instance, you will find a drop-down menu with your profile icon. Click on the drop-down and go to "Personal Settings". Backlog Integration @@ -90,7 +90,7 @@ LambdaTest integration with Backlog will help you file any UI bug on your Backlo ## Log Your First Bug From LambdaTest Integration With Backlog *** -**Step 1:** Go for any of the test from the left navigation menu. For demo, we will be taking “Real Time Test” option. +**Step 1:** Go for any of the test from the left navigation menu. For demo, we will be taking "Real Time Test" option. **Step 2:** Present a URL of the web-app you need to test in the dialog box. After that, select any configuration for browser and operating system of your choice & hit ‘Start‘. @@ -100,15 +100,15 @@ LambdaTest integration with Backlog will help you file any UI bug on your Backlo Backlog Integration -**Step 4:** After a screenshot is captured, you can annotate any issue or a task with an in-built image editor. Once you are done highlighting the bug, click on the button that says “Mark as Bug”. +**Step 4:** After a screenshot is captured, you can annotate any issue or a task with an in-built image editor. Once you are done highlighting the bug, click on the button that says "Mark as Bug". Backlog Integration -**Step 5:** After clicking on “Mark as Bug” button a form specific to Backlog would open up. Fill the fields as per your requirement, and create the issue. +**Step 5:** After clicking on "Mark as Bug" button a form specific to Backlog would open up. Fill the fields as per your requirement, and create the issue. Backlog Integration -> Note: After you click on “Create Bug”, you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message “Bug successfully marked” indicating that the screenshot has been pushed to your Backlog project. +> Note: After you click on "Create Bug", you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message "Bug successfully marked" indicating that the screenshot has been pushed to your Backlog project. Backlog Integration diff --git a/docs/bamboo-integration.md b/docs/bamboo-integration.md index b770e2b8d..1d5fa1d9f 100644 --- a/docs/bamboo-integration.md +++ b/docs/bamboo-integration.md @@ -78,7 +78,7 @@ LambdaTest provides an integration with Bamboo, using which you can perform cros Bamboo Integration -**Step 4:** To create your first task, “Source Code Checkout,” you need to fetch the relevant Git repository. +**Step 4:** To create your first task, "Source Code Checkout," you need to fetch the relevant Git repository. **Step 5:** Task number two would require to you install the required package for npm. diff --git a/docs/breeze-integration.md b/docs/breeze-integration.md index 4a1ae433e..16f7a056c 100644 --- a/docs/breeze-integration.md +++ b/docs/breeze-integration.md @@ -84,7 +84,7 @@ When two different applications interact with each other, a server-to-server com ## Log Your First Bug Through LambdaTest Integration With Breeze *** -**Step 1:** Go for any of the test from the left navigation menu. For demo, we will be taking “Real Time Test” option. +**Step 1:** Go for any of the test from the left navigation menu. For demo, we will be taking "Real Time Test" option. **Step 2:** Present a URL of the web-app you need to test in the dialog box. After that, select any configuration for browser and operating system of your choice & hit ‘Start‘. @@ -94,11 +94,11 @@ When two different applications interact with each other, a server-to-server com bug icon -**Step 4:** After a screenshot is captured, you can annotate any issue or a task with an in-built image editor. Once you are done highlighting the bug, click on the button that says “Mark as Bug”. +**Step 4:** After a screenshot is captured, you can annotate any issue or a task with an in-built image editor. Once you are done highlighting the bug, click on the button that says "Mark as Bug". mark as bug -**Step 5:** After clicking on “Mark as Bug” button a form would open up. Fill the fields as per your requirement, and create the issue. +**Step 5:** After clicking on "Mark as Bug" button a form would open up. Fill the fields as per your requirement, and create the issue. --- @@ -111,7 +111,7 @@ When two different applications interact with each other, a server-to-server com breeze integration bug -> Note: After you click on “Create Bug”, you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message “Bug successfully marked” indicating that the screenshot has been pushed to your Breeze project. +> Note: After you click on "Create Bug", you will be able to observe it being successfully marked through a single click effort. You will get prompt messages on top of your Virtual Machine indicating the progress of bug logging. After few seconds you will be notified with a prompt message "Bug successfully marked" indicating that the screenshot has been pushed to your Breeze project. breeze integration diff --git a/docs/bugherd-integration.md b/docs/bugherd-integration.md index 4becf6aca..45af69658 100644 --- a/docs/bugherd-integration.md +++ b/docs/bugherd-integration.md @@ -68,7 +68,7 @@ LambdaTest integrates with BugHerd, allowing users to file issues directly from :::info Fetch your Bugherd API Token - Visit your BugHerd account -> **Settings** tab. -- You will find the “**API Token**” under the section **Authentication Token**. Copy your API token. +- You will find the "**API Token**" under the section **Authentication Token**. Copy your API token.