-
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.
Merge pull request #539 from testsigmahq/dev
Created new doc for GenAI features, updated Okta SSO and GenAI docs
- Loading branch information
Showing
33 changed files
with
375 additions
and
205 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,8 +1,8 @@ | ||
| name: "CD" | ||
| name: 'CD' | ||
| on: | ||
| push: | ||
| branches: | ||
| - "main" | ||
| - 'main' | ||
| jobs: | ||
| Deploy: | ||
| runs-on: ubuntu-latest | ||
|
|
@@ -15,13 +15,13 @@ jobs: | |
| - name: Setup Node 18 | ||
| uses: actions/setup-node@v2 | ||
| with: | ||
| node-version: "18" | ||
| node-version: '18' | ||
| - name: Install dependencies | ||
| run: | | ||
| npm i --force --unsafe-perm | ||
| - name: Force installing sharp | ||
| run: npm install --ignore-scripts=false --verbose [email protected] --unsafe-perm --force | ||
| - name: "Create env file" | ||
| - name: 'Create env file' | ||
| run: | | ||
| rm -rf .env | ||
| touch .env | ||
|
|
@@ -41,11 +41,11 @@ jobs: | |
| cat .env | ||
| - name: Build | ||
| run: | | ||
| PREFIX_PATHS=true npm run build && npm run deploy | ||
| PREFIX_PATHS=true npm run clean && npm run build && npm run deploy | ||
| env: | ||
| AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} | ||
| AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} | ||
| AWS_DEFAULT_REGION: "us-east-1" | ||
| AWS_DEFAULT_REGION: 'us-east-1' | ||
| AWS_DEFAULT_OUTPUT: json | ||
| TYPESENSE_HOST: ${{ secrets.TYPESENSE_HOST }} | ||
| TYPESENSE_PORT: ${{ secrets.TYPESENSE_PORT }} | ||
|
|
||
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,8 +1,8 @@ | ||
| name: "Staging CD" | ||
| name: 'Staging CD' | ||
| on: | ||
| push: | ||
| branches: | ||
| - "dev" | ||
| - 'dev' | ||
| jobs: | ||
| StagingDeploy: | ||
| runs-on: ubuntu-latest | ||
|
|
@@ -15,14 +15,14 @@ jobs: | |
| - name: Setup Node 18 | ||
| uses: actions/setup-node@v2 | ||
| with: | ||
| node-version: "18" | ||
| node-version: '18' | ||
| - name: Install dependencies | ||
| run: | | ||
| rm -rf .cache node_modules | ||
| npm i --force --unsafe-perm | ||
| - name: Force installing sharp | ||
| run: npm install --ignore-scripts=false --verbose [email protected] --unsafe-perm --force | ||
| - name: "Create env file" | ||
| - name: 'Create env file' | ||
| run: | | ||
| rm -rf .env | ||
| touch .env | ||
|
|
@@ -44,11 +44,11 @@ jobs: | |
| run: sed -i 's/localhost/website.testsigma.com/g' src/environment.ts | ||
| - name: Build | ||
| run: | | ||
| PREFIX_PATHS=true npm run build && npm run deploy | ||
| PREFIX_PATHS=true npm run clean && npm run build && npm run deploy | ||
| env: | ||
| AWS_ACCESS_KEY_ID: ${{ secrets.WEBSITE_STAGING_AWS_ACCESS_KEY_ID }} | ||
| AWS_SECRET_ACCESS_KEY: ${{ secrets.WEBSITE_STAGING_AWS_SECRET_ACCESS_KEY }} | ||
| AWS_DEFAULT_REGION: "us-east-1" | ||
| AWS_DEFAULT_REGION: 'us-east-1' | ||
| AWS_DEFAULT_OUTPUT: json | ||
| TYPESENSE_HOST: ${{ secrets.WEBSITE_STAGING_TYPESENSE_HOST }} | ||
| TYPESENSE_PORT: ${{ secrets.WEBSITE_STAGING_TYPESENSE_PORT }} | ||
|
|
||
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,95 @@ | ||
| --- | ||
| title: "AI Test Automation with Testsigma Copilot" | ||
| page_title: "AI Test Automation with Testsigma Copilot" | ||
| metadesc: "In Testsigma you can now generate diverse test scenarios with a single click and also comprehensive test cases using simple prompts using GenAI" | ||
| noindex: false | ||
| order: 31.1 | ||
| page_id: "Testsigma for Windows Automation" | ||
| warning: false | ||
| contextual_links: | ||
| - type: section | ||
| name: "Contents" | ||
| - type: link | ||
| name: "Prerequisites" | ||
| url: "#prerequisites" | ||
| - type: link | ||
| name: "Generate Test Scenarios" | ||
| url: "#generate-test-scenarios" | ||
| - type: link | ||
| name: "Generate Test Steps with Prompts" | ||
| url: "#generate-test-steps-with-prompts" | ||
| --- | ||
|
|
||
| --- | ||
|
|
||
| Testsigma Copilot redefines test automation with the power of generative AI 🤖. | ||
|
|
||
| - You can effortlessly create diverse test scenarios with a single click. | ||
| - Generate detailed test steps that accurately mimic real-world user behavior with the right UI elements and complex user interactions. | ||
| - Create a comprehensive test case using simple prompts. | ||
|
|
||
|
|
||
| --- | ||
|
|
||
| > ## **Prerequisites** | ||
| > | ||
| > Before you begin, enable AI Features from **Settings > Preferences > Generative AI features** and ensure you're familiar with the concepts of [Test Cases](https://testsigma.com/docs/test-cases/manage/add-edit-delete/). | ||
|
|
||
| --- | ||
|
|
||
| ## **Generate Test Scenarios** | ||
|
|
||
| 1. From the left-side navbar, select **Create Tests > Test Cases** and then click **Create Test Case**. | ||
|
|
||
|  | ||
|
|
||
| 2. On the **Test Case Details** page, enter a name for the test case and click **Record** in the top-right corner. A new window will open. | ||
|
|
||
|  | ||
|
|
||
| 3. In the opened window, input the URL of the web page from which you want to generate test scenarios. The **Testsigma Recorder** will activate and prepare for recording. | ||
|
|
||
| 4. Click **Testsigma Copilot**. | ||
|  | ||
|
|
||
| 5. Click **Generate Scenarios** in the **Testsigma Copilot** overlay. The Testsigma Copilot will start generating test scenarios based on the current page content. | ||
|
|
||
|  | ||
|
|
||
| 6. Wait until the test scenarios are generated. | ||
|
|
||
| 7. Click on any generated test case scenario to view its corresponding test steps. | ||
|
|
||
|  | ||
|
|
||
| 8. Click **Add to test case** to import the displayed test steps into the recorder. | ||
|
|
||
|  | ||
|
|
||
| 9. Modify the test steps as per the desired test case behavior. Once the necessary modifications are done, click **Stop** to return to the test case details page. | ||
|
|
||
|  | ||
|
|
||
| --- | ||
|
|
||
| ## **Generate Test Steps with Prompts** | ||
|
|
||
| Follow the same steps from 1-3 from the above section. | ||
|
|
||
| 4. On prompt input, enter the prompt for which you want to fetch test steps. | ||
|  | ||
|
|
||
| 5. Press **Enter**. | ||
|
|
||
| 6. Wait until the test steps are generated. | ||
|
|
||
| 7. Click **Add to test case** to import the displayed test steps into the recorder. | ||
|
|
||
|  | ||
|
|
||
| 8. Modify the test steps as per the desired test case behavior. Once the necessary modifications are done, click **Stop** to return to the test case details page. | ||
|
|
||
|  | ||
|
|
||
| --- |
Oops, something went wrong.