Merge pull request LambdaTest#1358 from surishubham/main

Stage PR 1346,56

Author: surishubham

.github/workflows/pr.yml

@@ -46,5 +46,5 @@ jobs:
         name: Check spelling
         with:
           skip: "*.svg,*.js,*.map,*.css,*.scss,*.webp"
-          ignore_words_list: aks,atleast,cros,ddress,fiel,ist,nd,ot,pullrequest,ser,shttp,wast,fo,tht,extention,seldomly,delt,cruzer,plack,secur,te,testng,TestNG,FLE,fle,afterAll,afterall,Nome,nome,lod,pressEnter,pressenter,softwares
+          ignore_words_list: aks,atleast,cros,ddress,fiel,ist,nd,ot,pullrequest,ser,shttp,wast,fo,tht,extention,seldomly,delt,cruzer,plack,secur,te,testng,TestNG,FLE,fle,afterAll,afterall,Nome,nome,lod,pressEnter,pressenter,softwares,iif,IIF
           path: docs

assets/images/hyperexecute/knowledge-base/reports/custom-specflow.png

@@ -1,7 +1,7 @@
 ---
 id: azure-scim
 title: Azure AD Scim User Provisioning
-hide_title: true
+hide_title: false
 sidebar_label: Azure AD
 description: Integrating LambdaTest SCIM with Azure AD 
 keywords:
@@ -34,15 +34,7 @@ slug: scim/azure/
       })
     }}
 ></script>
-
-
-
-
-#   LambdaTest SCIM Auto User Provisioning with Azure AD
-
-* * *
-## Prerequisites ##
----
+## Prerequisites
 Integrate SCIM With LambdaTest:
 
 * You will need an Enterprise plan with LambdaTest.
@@ -77,17 +69,46 @@ Integrate SCIM With LambdaTest:
 **Step 8:** Under the Mappings section, select Synchronize Azure Active Directory Users.
 <img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/mapping-tab.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
 
-**Step 9:** Review the User Attribute mappings:
-<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/attribute-mapping.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+**Step 9:** Creating Custom Attributes
+
+- Show advanced options > Edit attribute list for customappsso > Add attributes
+- userName, Active, name.givenName, name.familyName are required attributes
 
-userName, Active, name.givenName, name.familyName are required attributes
+<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/userName.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+ 
+- **`urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:OrganizationRole`**: Custom attribute used to set LambdaTest Organization Role for Users, If this attribute is not mapped User role would be set by default. Allowed values are (Admin/Guest/User)
 
-**urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:OrganizationRole**: Custom attribute used to set LambdaTest Organization Role for Users, If this attribute is not mapped **User** role would be set by default. Allowed values are (Admin/Guest/User)
+- **`urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:LambdatestGroup`**: Used to assign an existing group in Lambdatest to a new user created in lambdatest through SCIM. (Applicable only if organisation has group support active)
 
 For filtering only **userName** attribute is supported and must be selected for filtering, click edit on userPrincipalName and make sure **Apply this mapping** is set to **Always**
 
-<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/userName.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/attribute-mapping.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+
+- **Dynamic/Static assignment of custom attributes**: After custom attribute creation, we have to map them using “Add new mapping”
 
+<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/dynamic_1.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+
+<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/dynamic_2.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+
+
+Now there are three types Mapping type in AzureAD, “Direct”, “Constant” and “Expression”.
+
+
+For example we can set Constant association “Guest” for `urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:OrganizationRole`
+
+<img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/dynamic_3.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
+
+Or, can create association using the Expression like this ,
+
+```javascript
+IIF(SingleAppRoleAssignment([appRoleAssignments])="Admin", "Admin",
+IIF(SingleAppRoleAssignment([appRoleAssignments])="Guest", "Guest",
+IIF(SingleAppRoleAssignment([appRoleAssignments])="User", "User", "User")))
+```
+
+In the above example we are using the appRoleAssignments attribute of microsoft user to set string value.
+
+After custom attribute creation, we have to map them using “Add new mapping”
 
 **Step 10:** To enable the Azure AD provisioning service for LambdaTest, change the Provisioning Status to On in the Settings section.
 <img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/provisioning-on.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
@@ -99,7 +120,6 @@ This operation starts the initial synchronization cycle of all users in Scope in
 <img loading="lazy" src={require('../assets/images/lambdatest-scim/azure-ad/save.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
 
 
-
 > That's all you need to know about LambdaTest SCIM Auto User Provisioning with Azure AD.In case you have any questions please feel free to reach out to us via the <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24/7 chat support**</span> or email us over [[email protected]](mailto:[email protected]).
 
 

assets/images/lambdatest-scim/azure-ad/dynamic_1.png

@@ -0,0 +1,88 @@
+---
+id: custom-speclow-report
+title: Custom Specflow Report
+sidebar_label: Custom Specflow
+description: Custom specflow report
+keywords:
+  - LambdaTest Hyperexecute
+  - LambdaTest Hyperexecute help
+  - LambdaTest Hyperexecute documentation
+url: https://www.lambdatest.com/support/docs/custom-speclow-report/
+site_name: LambdaTest
+slug: custom-speclow-report/
+---
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "HyperExecute Custom Specflow Report",
+          "item": "https://www.lambdatest.com/support/docs/custom-speclow-report/"
+        }]
+      })
+    }}
+></script>
+This guide provides step-by-step instructions on how to generate a custom SpecFlow report in LambdaTest HyperExecute. By following the specified changes in the YAML file and modifying the test script, users can receive detailed test reports via email.
+
+## Prerequisites
+- A valid LambdaTest account.
+- A configured HyperExecute environment.
+- A SpecFlow-based test suite.
+
+## Configuration Changes
+To enable custom SpecFlow reporting, make the following changes to your YAML configuration file and test script.
+
+### Step 1: Modify the YAML Configuration File
+Add the following settings in your YAML file to enable reporting and configure partial reports:
+
+```yaml
+report: true
+partialReports:
+  location: YOUR_REPORTS_LOCATION
+  type: xml
+  frameworkName: specflow-custom
+  email:
+    to: [YOUR_EMAIL_ID]
+    metaInfo: [ "project-name:YOUR_CUSTOM_PROJECT_NAME", "project-env: YOUR_CUSTOM_PROJECT_ENV" ]
+```
+
+Explanation:
+- `report: true` → Enables the reporting feature.
+- `partialReports.location` → Specifies the directory where the partial reports will be stored.
+- `partialReports.type: xml` → Configures the report format as XML.
+- `partialReports.frameworkName: specflow-custom` → Sets the framework name.
+- `email.to` → Defines the recipient email address where the reports will be sent.
+- `email.metaInfo` → Adds metadata, including project name and environment details, to the report.
+
+### Step 2: Modify the Test Script
+Add the following capability in your test script to ensure the correct execution status is recorded:
+
+`((IJavaScriptExecutor)driver).ExecuteScript($"lambda-info=suitename:YOUR_SUITE_NAME:passed");`
+
+Explanation:
+- This script sends test execution information (suite name and status) to LambdaTest.
+- Replace `YOUR_SUITE_NAME` with the appropriate suite name.
+- The passed status can be dynamically changed based on the test result.
+
+### Step 3: Report Generation and Email Notification
+Once the tests are executed, the custom SpecFlow report will be generated and sent to the configured email address. The report will include:
+
+- Tag-based test summaries and details.
+- Suite-based test summaries and details.
+- Number of tests passed, failed, skipped, or with other statuses.
+- Meta information such as project name and environment.
+
+<img loading="lazy" src={require('../assets/images/hyperexecute/knowledge-base/reports/custom-specflow.png').default} alt="Image" className="doc_img"/> 

assets/images/lambdatest-scim/azure-ad/dynamic_2.png

@@ -1,7 +1,7 @@
 ---
 id: okta-scim
 title: Okta Scim User Provisioning
-hide_title: true
+hide_title: false
 sidebar_label: Okta
 description: Integrating LambdaTest SCIM with Okta 
 keywords:
@@ -35,18 +35,11 @@ slug: scim/okta/
     }}
 ></script>
 
-
-
-
-#   LambdaTest SCIM Auto User Provisioning with Okta
-
-* * *
-## Prerequisites ##
----
+## Prerequisites
 Integrate SCIM With LambdaTest:
 
-* You will need an Enterprise plan with LambdaTest.
-* SSO must be already integrated. Please complete [LambdaTest SSO & Okta Integration](/support/docs/lambdatest-sso-okta-integration/)
+- You will need an Enterprise plan with LambdaTest.
+- SSO must be already integrated. Please complete [LambdaTest SSO & Okta Integration](/support/docs/lambdatest-sso-okta-integration/)
 
 ## Integrating SCIM with Okta
 **Step 1:** Sign in to your LambdaTest account. Don't have an account, [register for free](https://accounts.lambdatest.com/register).
@@ -83,11 +76,13 @@ Click Test Connection to ensure Okta can connect to LambdaTest. If the connectio
 
 userName, Active, name.givenName, name.familyName are required attributes
 
-***Creating Custom Attributes***
+**Creating Custom Attributes**
+
+For creating custom attribute in Okta, go to Directory > Profile Editor > Add Attribute > [Create Custom Attribute](https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-add-custom-user-attributes.htm)
 
-**urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:OrganizationRole**: 
+**`urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:OrganizationRole`**: 
 
-For creating custom attribute in Okta, go to Directory > Profile Editor > Add Attribute ([Create Custom Attribute](https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-add-custom-user-attributes.htm))
+**`urn:ietf:params:scim:schemas:extension:LambdaTest:2.0:User:LambdatestGroup`** : Applicable only if organisation has group support active)
 
 Enter Display Name as per your choice 
 Enter Variable name as **OrganizationRole**
@@ -100,9 +95,9 @@ Select Enum as **Yes**
 Enter the values as **Admin, Guest, User**
 <img loading="lazy" src={require('../assets/images/sso/img_19.png').default} alt="okta integration" width="944" height="487" className="doc_img"/>
 
+Also if you want to assign this attribute at a okta group level choose AttributeType as Group
 
-
-
+<img loading="lazy" src={require('../assets/images/sso/img_20.png').default} alt="okta integration" width="944" height="487" className="doc_img"/>
 
 **Step 10:** To enable the Okta provisioning service for LambdaTest, set Create Users, Update User Attributes and Deactivate Users to enabled
 <img loading="lazy" src={require('../assets/images/lambdatest-scim/okta/provisioning-enabled.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>

assets/images/lambdatest-scim/azure-ad/dynamic_3.png

@@ -1,7 +1,7 @@
 ---
 id: scim
 title: Getting Started With Scim User Provisioning
-hide_title: true
+hide_title: false
 sidebar_label: SCIM
 description: The SCIM specification is designed to make managing user identities easier. SCIM allows your Identity Provider (IdP) to manage users within your LambdaTest workspace  
 keywords:
@@ -34,41 +34,24 @@ slug: scim/
       })
     }}
 ></script>
-
-
-
-
-# Getting Started With SCIM Auto User Provisioning
-
-* * *
-
 The SCIM specification is designed to make managing user identities easier. SCIM allows your Identity Provider (IdP) to manage users within your LambdaTest workspace
 > SSO must be integrated before enabling SCIM. Please see [Getting Started With Single Sign On (SSO)](/support/docs/single-sign-on/) or [[email protected]](mailto:[email protected]) for questions.
 
 ## Benefits Of SCIM
+Here are the following benefits of integrating SCIM with LambdaTest:
 
-* * *
-
-Here are the following benefits of integrating SCIM with LambdaTest
+- **Efficiency and Automation**: SCIM automates the process of user identity management, making it more efficient and less error-prone. It enables automatic provisioning and de-provisioning of user accounts, reducing manual administrative tasks and associated errors.
+- **Consistency:**: SCIM ensures that user data is consistent across different systems and services. When a user's attributes (like role) are updated in the identity provider, SCIM can be used to propagate those changes to all connected service providers, maintaining accurate and up-to-date information.
+- **Security and Access Control:**:  By centralizing identity management through SCIM, organizations can better enforce access control policies and ensure that users have appropriate access rights to the resources they need. This can help mitigate security risks associated with improper access permissions.
+- **Assigning Groups to Users (If Groups Are Activated in Your Organization) :** If your organization has group functionality enabled, you can assign existing LambdaTest groups to users provisioned through an Identity Provider (IdP) such as Microsoft Azure AD, Okta, and others using SCIM. 
+> Connect with our [24/7 customer support](mailto:[email protected]) team to get the **Group** feature enabled for your organization.
 
-*   **Efficiency and Automation**: SCIM automates the process of user identity management, making it more efficient and less error-prone. It enables automatic provisioning and de-provisioning of user accounts, reducing manual administrative tasks and associated errors.
-
-*   **Consistency:**: SCIM ensures that user data is consistent across different systems and services. When a user's attributes (like role) are updated in the identity provider, SCIM can be used to propagate those changes to all connected service providers, maintaining accurate and up-to-date information.
-  
-* **Security and Access Control:**:  By centralizing identity management through SCIM, organizations can better enforce access control policies and ensure that users have appropriate access rights to the resources they need. This can help mitigate security risks associated with improper access permissions.
 
 ## Feature Of SCIM
-
-* * *
-
 LambdaTest provides the support for the below SCIM features.
 
-*   **User Provisioning and De-provisioning**:  SCIM facilitates the automatic provisioning and de-provisioning of user accounts across different systems and services. When a user is added or removed from the identity provider, SCIM can be used to propagate these changes to your LambdaTest account.
-
-*   **Updating User Attributes**: Using SCIM you can update user attribute such as **Organization Role** directly from your Identity Provider.
-
-## Enable LambdaTest SCIM
-***
+- **User Provisioning and De-provisioning**:  SCIM facilitates the automatic provisioning and de-provisioning of user accounts across different systems and services. When a user is added or removed from the identity provider, SCIM can be used to propagate these changes to your LambdaTest account.
+- **Updating User Attributes**: Using SCIM you can update user attribute such as **Organization Role** directly from your Identity Provider.
 
 ## Copy SCIM Base URL and Bearer Token (Auth Header Required by IdP)
 **Step 1:** Sign in to your LambdaTest account. Don't have an account, [register for free](https://accounts.lambdatest.com/register).
@@ -84,7 +67,7 @@ LambdaTest provides the support for the below SCIM features.
 <img loading="lazy" src={require('../assets/images/lambdatest-scim/scim-base-url.png').default} alt="Image" width="404" height="206"  className="doc_img img_center"/><br/>
 
 ## SCIM User Attributes
-```json
+```javascript
 {
     "schemas": [
         "urn:ietf:params:scim:schemas:core:2.0:User",
@@ -134,7 +117,7 @@ User accounts can only be deactivated (active:false) via PUT/PATCH or DELETE Use
 
 POST `https://auth.lambdatest.com/api/scim/Users`
 
-```json
+```javascript
 {
   "schemas": [
     "urn:ietf:params:scim:schemas:core:2.0:User",