Merge pull request #2 from techconative/configName

Config name support

.github/workflows/release.yml

@@ -0,0 +1,31 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20.x'
+
+      - name: Install Dependencies
+        run: npm install
+
+      - name: Build
+        run: npm run build
+
+      - name: Semantic Release
+        run: npx semantic-release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.releaserc.yaml

@@ -0,0 +1,11 @@
+branches:
+  - main
+
+plugins:
+  - - "@semantic-release/commit-analyzer"
+  - - "@semantic-release/release-notes-generator"
+  - - "@semantic-release/npm"
+  - - "@semantic-release/git"
+    - assets:
+      - package.json
+      message: "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"

README.md

@@ -9,11 +9,11 @@ Core features:
 
 * Support for Jasmine/Jest/Mocha and Cucumber runtime frameworks
 * Test results are aggregated under the same test run if you are executing more spec(test) files and they are belongs to the same suite
+* Using Azure Configurations, test results can be categorized as per the configuration (dev/stage/prod) used
 * Results are reported immediately after single test execution (real-time reporting)
 * Test run is closed after last spec(test) file has been finished
 * Multi suite support
 
-
 ## Installation
 
 Install this module locally with the following command to be used as a (dev-)dependency:
@@ -53,6 +53,7 @@ exports.config = {
                   planId: 263072,
                   suiteId: 263073,
                   runName: 'FE regression tests for TestPlan',
+                  configurationName: 'stage'
               },
           ],
     ],
@@ -89,10 +90,15 @@ Scenario Can authenticate a valid user
 
 ### Azure DevOps Report Example
 
-This is an example of the results pushed on AZ Test Plans, during a test run
+#### This is an example of the results pushed on AZ Test Plans, during a test run
 ![AzureDevops Test Plans example](./img/AZ-DevOps-example.png)
 
-<br>
+#### If you have multiple Configurations, using `configurationName` test results can be categorized
+![AzureDevops Test Plans Configurations](./img/AZ-config.png)
+
+![AzureDevops Test Results History](./img/AZ-resultHistory.png)
+
+![AzureDevops Test Point History](./img/AZ-testpointHistory.png)
 
 ## Service Options
 
@@ -167,3 +173,13 @@ Type: `string`
 Default: `"@?[cC](\d+)"`
 
 Required: `false`
+
+### configurationName
+
+If you have multiple Configurations in Azure (Test Plans - Configurations) apart from the default-one, you need to mention the configuration name to filter the test points as per the configuration while creating test run & update test results.
+
+Example: `"prod"`
+
+Type: `string`
+
+Required: `false`