-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added Following Salesforce Documents
- Loading branch information
1 parent
2f53450
commit 75d639c
Showing
7 changed files
with
345 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
100 changes: 96 additions & 4 deletions
100
src/pages/docs/salesforce-testing/metadata-connections.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,19 +1,111 @@ | ||
| --- | ||
| title: "Creating Metadata Connections" | ||
| page_title: "Introduction: Testsigma for Salesforce Test Automation" | ||
| metadesc: "Salesforce Testing with Testsigma helps reduce average test authoring time by 50%, and test case execution will be 2X faster with a user-friendly interface" | ||
| page_title: "Metadata Connections" | ||
| metadesc: "A Metadata connection enables actions like refreshing metadata, configurations, creating objects, & managing components that define how the application behaves" | ||
| noindex: false | ||
| order: 29.4 | ||
| page_id: "Testsigma for Salesforce Test Automation" | ||
| page_id: "Creating Metadata Connections" | ||
| warning: false | ||
| contextual_links: | ||
| - type: section | ||
| name: "Contents" | ||
| - type: link | ||
| name: "Prerequisites" | ||
| url: "#prerequisites" | ||
| - type: link | ||
| name: "Steps to Create Metadata Connection" | ||
| url: "#steps-to-create-metadata-connection" | ||
| - type: link | ||
| name: "Steps to Edit Metadata Connection" | ||
| url: "#steps-to-edit-metadata-connection" | ||
| - type: link | ||
| name: "Steps to Refresh Metadata Connection" | ||
| url: "#steps-to-refresh-metadata-connection" | ||
| --- | ||
|
|
||
| --- | ||
|
|
||
| In Testsigma, you can create a Salesforce application and establish a Metadata connection, which enables you to perform various actions like retrieving metadata, updating configurations, creating custom objects, and managing other components that define how the application behaves. This article discusses creating a metadata connection in Testsigma. | ||
|
|
||
| --- | ||
|
|
||
| ## **Prerequisites** | ||
|
|
||
| - You need to have Salesforce org with test setup | ||
| - Salesforce connected app | ||
|
|
||
| --- | ||
|
|
||
| ## **Steps to Create Metadata Connection** | ||
|
|
||
| 1. Click on **Create metadata connection** on **Salesforce connections page**. | ||
|  | ||
|
|
||
| 2. This will open the **Metadata connection** prompt. | ||
|  | ||
|
|
||
| 3. On **Metadata connection** prompt, | ||
| - Enter **Connection name**, which is generally the user role you connect through, e.g., **Admin**. | ||
|  | ||
| [[info | **NOTE**:]] | ||
| | You can also choose a custom name for the connection. | ||
| - Choose the **Production / Developer edition**, if you’re testing the product environment or Sandbox, if you’re testing the staging environment from **Connect with** dropdown. | ||
|  | ||
| - Choose the **Authentication type** from the dropdown. In this example, we are choosing **OAuth 2.0**. | ||
|  | ||
|
|
||
| <details style="border: 1px solid gray; border-radius: 4px; padding: 0.5em; margin: 0.5em 0; background-color: #f2f2f2;"> | ||
| <summary style="color: darkgreen; font-weight: bold; list-style: none;" onclick="if(this.parentNode.open) this.parentNode.style.border='1px solid gray'; else this.parentNode.style.border='none';"> | ||
| <span style="margin-right: 5px;">ℹ️</span>Authentication Types: | ||
| </summary><br> | ||
| There are two ways to Authenticate: | ||
| <ul> | ||
| <li><b>User name & Password:</b> For User name & Password, enter Username, Password, Security token, Consumer key, and Consumer secret. </li> | ||
| <li><b>OAuth</b> For OAuth, enter Username, Consumer key, Consumer secret and Callback URL.</li> | ||
| </ul> | ||
| </details> | ||
|
|
||
| - Click on **Authorise & Connect**. | ||
|  | ||
|
|
||
| - A new window will open up requesting for **Salesforce Login**. Enter the credentials and click on **Log In**. | ||
|  | ||
|
|
||
| - This will display the **Environment** associated with the credentials. Click on **Start metadata sync**. | ||
|  | ||
|
|
||
| - Wait until the sync is complete. This will take some time. | ||
|  | ||
|
|
||
| 4. Once Metadata sync is successful, you can create test cases by clicking **Create Test Case**. | ||
|  | ||
|
|
||
| --- | ||
|
|
||
| ## **Steps to Edit Metadata Connection** | ||
|
|
||
| 1. From the **Dashboard**, click on **SF Connections**. | ||
|  | ||
|
|
||
| 2. In the **Metadata connection** section, hover over the connection, click on the kebab menu, and choose **Edit connection** from the dropdown menu. | ||
|  | ||
|
|
||
| 3. On the **Metadata connection** prompt, make the necessary changes and click on **Authorise & Connect**. | ||
|  | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | You can not update the Metadata connection with a different environment. | ||
|
|
||
| --- | ||
|
|
||
| Coming Soon! | ||
| ## **Steps to Refresh Metadata Connection** | ||
|
|
||
| To refresh metadata, you have two options: | ||
|
|
||
| 1. From the **Dashboard**, go to **SF Connections** and click on **Refresh Metadata**. | ||
|  | ||
|
|
||
| 2. Click on **Refresh Metadata** directly from the dashboard. | ||
|  | ||
|
|
||
| --- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,20 +1,93 @@ | ||
| --- | ||
| title: "Test Cases for Salesforce" | ||
| page_title: "Introduction: Testsigma for Salesforce Test Automation" | ||
| metadesc: "Salesforce Testing with Testsigma helps reduce average test authoring time by 50%, and test case execution will be 2X faster with a user-friendly interface" | ||
| title: "Test Cases for Salesforce (Manual + Live)" | ||
| page_title: "Build Test Cases for Salesforce Testing" | ||
| metadesc: "Creating test cases for Salesforce automation is easy with Salesforce metadata artifacts and capabilities from Testsigma like smart NLPs, and the debugger" | ||
| noindex: false | ||
| order: 29.6 | ||
| page_id: "Testsigma for Salesforce Test Automation" | ||
| page_id: "Test Cases for Salesforce" | ||
| warning: false | ||
| contextual_links: | ||
| - type: section | ||
| name: "Contents" | ||
| - type: link | ||
| name: "Prerequisites" | ||
| url: "#prerequisites" | ||
| - type: link | ||
| name: "Steps to Create Test Cases for Salesforce" | ||
| url: "#steps-to-create-test-cases-for-salesforce" | ||
| - type: link | ||
| name: "Sample Test Case for Salesforce Automation" | ||
| url: "#sample-test-case-for-salesforce-automation" | ||
| --- | ||
|
|
||
|
|
||
| --- | ||
|
|
||
| With Testsigma, creating test cases for Salesforce is easy as we can leverage Metadata artifacts, smart NLPs, and the debugger to Automate Salesforce Testing. Metadata artifacts help auto-learn Salesforce components, smart NLPs simplify test scenario expression, and the debugger facilitates real-time test authoring. This article discusses creating test cases for Salesforce Automation and using the debugger for Live Test Authoring in Testsigma. | ||
|
|
||
| Here’s a quick video demonstrating how create test cases for Salesforce testing. | ||
|
|
||
| <iframe width="560" height="315" src="https://www.youtube.com/embed/bbhvPHlZ4MU?si=GtyrMu8FUWfEfDgP" title="Build Test Cases for Salesforce Testing with Ease!" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> | ||
|
|
||
| --- | ||
|
|
||
| Coming Soon! | ||
| ## **Prerequisites** | ||
|
|
||
| - A Salesforce organization with the test setup | ||
| - A Salesforce connected app | ||
| - Salesforce metadata connected to Testsigma | ||
| - [Testsigma Chrome Extension](https://chromewebstore.google.com/detail/testsigma-recorder/epmomlhdjfgdobefcpocockpjihaabdp) | ||
|
|
||
| --- | ||
|
|
||
| ## **Steps to Create Test Cases for Salesforce** | ||
|
|
||
| 1. Navigate to **Create Tests > Test Cases** and click on **Create Test Case**. | ||
|  | ||
|
|
||
| 2. From the **Test Case Details** page, you can create the test steps for your test case using either of the following methods: | ||
| - Write test steps manually using **Smart NLPs** by clicking **Add new step**. | ||
| - Use **Recorder** to record steps. | ||
|  | ||
|
|
||
| 3. Once the test steps are created, click on **Run** to execute the Test Case. | ||
|  | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | For advanced options, refer to [test case advanced options](https://testsigma.com/docs/test-cases/manage/add-edit-delete/#test-case----advanced-options). | ||
|
|
||
| --- | ||
|
|
||
| ## **Sample Test Case for Salesforce Automation** | ||
| Let's say we have a scenario where we want to log in to Salesforce, navigate to the Sales tab, create a Lead record, and Edit the record form. Regular UI interactions require a lot of steps. However, with Testsigma's smart NLPs, we can automate the same flow in just four steps. | ||
|
|
||
| 1. Use the NLP, **Login to Salesforce using *Salesforce Connection***. | ||
| Here, we can choose a connection or create a connection by clicking on **Add Connection**. | ||
|  | ||
|
|
||
| 2. Use the NLP, **Switch to *Application*** and replace application from the dropdown. | ||
|  | ||
|
|
||
| 3. Use the NLP, **Create record using *Salesforce Connection* in *Salesforce Object Form* and store *RECORD_ID* in variable *test data***. | ||
|  | ||
|
|
||
| This is API Step where we create a **Lead** record using **Salesforce Connection** in **Lead** and store the record ID in a **Variable**. We will use this variable to open the editing form with the **record ID**. | ||
|
|
||
| 4. Use the NLP, **Open edit form for record with *Record ID* on *Salesforce Object***. | ||
| Here, we open the edit form with the record ID stored in the variable in the previous step. | ||
|  | ||
|
|
||
| 5. Click on **Record**. This will open a Chrome window along with the test recorder. All the steps will be executed up to that point, and you can start recording UI interactions by clicking on the play icon. | ||
|  | ||
|
|
||
| 6. Perform the actions and click on **Stop Recording**. This will open the **Stop Web Debugger** warning prompt. | ||
|  | ||
|
|
||
| 7. On the **Stop Web Debugger** run warning prompt, click on **Stop**. | ||
|  | ||
|
|
||
| 8. Refresh the **Test Case Details** page to see all the recorded steps. | ||
|  | ||
|
|
||
|
|
||
| --- |
Oops, something went wrong.