chore(performance): Add readmes

tests/k6/tests/enduser/performance/README.md

@@ -0,0 +1,79 @@
+# Enduser get dialogs
+
+This directory holds a performance test for all GET endpoints for `api/v1/enduser/dialogs`. The performance test is implemented in the `enduser-search.js` file. The purpose of this test is to measure the response time and performance of each endpoint when accessed sequentially for different end users. By running this test, you can identify any bottlenecks or performance issues in the API. This test can be executed from the command line or as part of a GitHub Actions workflow. For more information on how to run the test and view the results, refer to the sections below.
+
+## Prerequisites
+- [K6 prerequisites](../../README.md#Prerequisites)
+
+## Test file
+The test file associated with this performance test is 
+- `enduser-search.js`
+
+## Test description
+The test has a list of enduser (ssn) with pregenerated tokens, and the following endpoints are visited in
+sequence for each enduser:
+- api/v1/enduser/dialogs?Party=urn:altinn:person:identifier-no:`<ssn>`
+- api/v1/enduser/dialogs/`<dialogId>`
+- api/v1/enduser/dialogs/`<dialogId>`/activities
+- api/v1/enduser/dialogs/`<dialogId>`/activities/`<activityId>`
+- api/v1/enduser/dialogs/`<dialogId>`/seenlog
+- api/v1/enduser/dialogs/`<dialogId>`/seenlog/`<seenlogId>`
+- api/v1/enduser/dialogs/`<dialogId>`/transmissions
+- api/v1/enduser/dialogs/`<dialogId>`/transmissions/`<transmissionId>`
+- api/v1/enduser/dialogs/`<dialogId>`/labellog
+
+## Run test
+### From cli
+1. Navigate to the following directory:
+```shell
+cd tests/k6/tests/enduser/performance
+```
+2. Generate tokens using the script below. Make sure to replace `<username>`, `<passwd>` and `<test|staging|yt01>` with your desired values:
+```shell
+TOKEN_GENERATOR_USERNAME=<username> \
+TOKEN_GENERATOR_PASSWORD=<passwd> API_ENVIRONMENT=<test|staging|yt01> \
+../../scripts/generate_tokens.sh ../../performancetest_data personal
+```
+3. Run the test using the following command. Replace `<test|staging|yt01>`, `<vus>`, and `<duration>` with the desired values:
+```shell
+k6 run enduser-search.js -e API_VERSION=v1 \
+-e API_ENVIRONMENT=<test|staging|yt01> \
+--vus=<vus> --duration=<duration>
+```
+4. Refer to the k6 documentation for more information on usage.
+
+### From Github Actions
+To run the performance test using GitHub Actions, follow these steps:
+1. Go to the [GitHub Actions](https://github.com/digdir/dialogporten/actions/workflows/dispatch-k6-performance.yml) page.
+2. Select "Run workflow" and fill in the required parameters.
+3. Tag the performance test with a descriptive name.
+
+### Github Action with act
+To run the performance test locally using GitHub Actions and act, perform the following steps:
+1. [Install act](https://nektosact.com/installation/).
+2. Navigate to the root of the repository.
+3. Create a `.secrets` file that matches the GitHub secrets used. Example:
+```file
+TOKEN_GENERATOR_USERNAME:**
+TOKEN_GENERATOR_PASSWORD:**
+K6_CLOUD_PROJECT_ID=**
+K6_CLOUD_TOKEN=**
+K6_PROMETHEUS_RW_USERNAME=**
+K6_PROMETHEUS_RW_PASSWORD=**
+K6_PROMETHEUS_RW_SERVER_URL=**
+```
+4. Run act using the command below. Replace `<vus>` and `<duration>` with the desired values:
+```shell
+act workflow_dispatch -j k6-performance -s GITHUB_TOKEN=`gh auth token` \
+--container-architecture linux/amd64 --artifact-server-path $HOME/.act \ 
+--input vus=<vus> --input duration=<duration> \ 
+--input testSuitePath=tests/k6/tests/enduser/performance/enduser-search.js \ 
+--input tokens=personal
+```
+
+## Test Results
+Test results can be found in github action run log and in appinsights. We are prepared for exporting results to grafana, but so far results are exported to a private grafana instance only, as can be seen from the `.secrets`listed earlier 
+
+## TODO
+Fix reporting
+

tests/k6/tests/graphql/README.md

@@ -0,0 +1,64 @@
+# Graphql get dialogs
+
+This directory holds a performance test with POST for `graphql`. The test file `graphql-search.js` is responsible for executing the performance test. It includes a list of end users (ssn) with pregenerated tokens and performs a POST request to the GraphQL endpoint with the payload `input: { party: ["urn:altinn:person:identifier-no:${identifier}"]}`. This test is designed to measure the performance of the GraphQL search functionality. 
+
+## Prerequisites
+- [K6 prerequisites](../../README.md#Prerequisites)
+
+## Test file
+The test file associated with this performance test is 
+- `graphql-search.js`
+
+## Run test
+### From cli
+1. Navigate to the following directory:
+```shell
+cd tests/k6/tests/graphql/performance
+```
+2. Generate tokens using the script below. Make sure to replace `<username>`, `<passwd>` and `(<test|staging|yt01>)` with your desired values:
+```shell
+TOKEN_GENERATOR_USERNAME=<username> \
+TOKEN_GENERATOR_PASSWORD=<passwd> API_ENVIRONMENT=<(test|staging|yt01)> \
+../../scripts/generate_tokens.sh ../../performancetest_data personal
+```
+3. Run the test using the following command. Replace `<(test|staging|yt01)>`, `<vus>`, and `<duration>` with the desired values:
+```shell
+k6 run graphql-search.js -e API_VERSION=v1 \
+-e API_ENVIRONMENT=<(test|staging|yt01)> \
+--vus=<vus> --duration=<duration>
+```
+4. Refer to the k6 documentation for more information on usage.
+### From Github Actions
+To run the performance test using GitHub Actions, follow these steps:
+1. Go to the [GitHub Actions](https://github.com/digdir/dialogporten/actions/workflows/dispatch-k6-performance.yml) page.
+2. Select "Run workflow" and fill in the required parameters.
+3. Tag the performance test with a descriptive name.
+
+### Github Action with act
+To run the performance test locally using GitHub Actions and act, perform the following steps:
+1. [Install act](https://nektosact.com/installation/).
+2. Navigate to the root of the repository.
+3. Create a `.secrets` file that matches the GitHub secrets used. Example:
+```file
+TOKEN_GENERATOR_USERNAME:**
+TOKEN_GENERATOR_PASSWORD:**
+K6_CLOUD_PROJECT_ID=**
+K6_CLOUD_TOKEN=**
+K6_PROMETHEUS_RW_USERNAME=**
+K6_PROMETHEUS_RW_PASSWORD=**
+K6_PROMETHEUS_RW_SERVER_URL=**
+```
+4. Run act using the command below. Replace `<vus>` and `<duration>` with the desired values:
+```shell
+act workflow_dispatch -j k6-performance -s GITHUB_TOKEN=`gh auth token` \
+--container-architecture linux/amd64 --artifact-server-path $HOME/.act \ 
+--input vus=<vus> --input duration=<duration> \ 
+--input testSuitePath=tests/k6/tests/graphql/performance/graphql-search.js \ 
+--input tokens=personal
+```
+
+## Test Results
+Test results can be found in github action run log and in appinsights. We are prepared for exporting results to grafana, but so far results are exported to a private grafana instance only, as can be seen from the `.secrets`listed earlier 
+
+## TODO
+Fix reporting

tests/k6/tests/serviceowner/performance/README.md

@@ -0,0 +1,100 @@
+## Service Owner Performance Test
+
+This performance test directory focuses on evaluating the GET and POST endpoints of the `serviceowner` API. The test files associated with this performance test are `create-dialog.js`, `create-remove-dialog.js`, `serviceowner-search.js`, and `purge-dialogs.js`. These files are designed to measure the performance and scalability of the API endpoints under different scenarios. By running these tests, you can gain insights into the system's response time, throughput, and resource utilization. Use the instructions below to execute the performance test and analyze the results.
+
+### Prerequisites
+Before running the performance test, make sure you have met the following prerequisites:
+- [K6 prerequisites](../../README.md#Prerequisites)
+
+### Test Files
+The test files associated with this performance test is 
+- `create-dialog.js`
+- `create-remove-dialog.js`
+- `serviceowner-search.js`
+- `purge-dialogs.js` (used for cleanup after test)
+
+### Run Test
+To run the performance test, follow the instructions below:
+
+#### From CLI
+1. Navigate to the following directory:
+```shell
+cd tests/k6/tests/serviceowner/performance
+```
+2. Generate tokens using the script below. Make sure to replace `<username>`, `<passwd>` and `<(test|staging|yt01)>` with your actual desired values:
+```shell
+TOKEN_GENERATOR_USERNAME=<username> \
+TOKEN_GENERATOR_PASSWORD=<passwd> API_ENVIRONMENT=<(test|staging|yt01)> \
+../../scripts/generate_tokens.sh ../../performancetest_data both
+```
+3. Run the test using the following command. Replace `<test-file>`, `<(test|staging|yt01)>`, `<vus>`, and `<duration>` with the desired values:
+```shell
+k6 run <test-file> -e API_VERSION=v1 \
+-e API_ENVIRONMENT=<(test|staging|yt01)> \
+--vus=<vus> --duration=<duration>
+```
+4. Refer to the k6 documentation for more information on usage.
+
+#### From GitHub Actions
+To run the performance test using GitHub Actions, follow these steps:
+1. Go to the [GitHub Actions](https://github.com/digdir/dialogporten/actions/workflows/dispatch-k6-performance.yml) page.
+2. Select "Run workflow" and fill in the required parameters.
+3. Tag the performance test with a descriptive name.
+
+#### GitHub Action with act
+To run the performance test locally using GitHub Actions and act, perform the following steps:
+1. [Install act](https://nektosact.com/installation/).
+2. Navigate to the root of the repository.
+3. Create a `.secrets` file that matches the GitHub secrets used. Example:
+```file
+TOKEN_GENERATOR_USERNAME:**
+TOKEN_GENERATOR_PASSWORD:**
+K6_CLOUD_PROJECT_ID=**
+K6_CLOUD_TOKEN=**
+K6_PROMETHEUS_RW_USERNAME=**
+K6_PROMETHEUS_RW_PASSWORD=**
+K6_PROMETHEUS_RW_SERVER_URL=**
+```
+4. Run act using the command below. Replace `<path-to-testscript>`, `<vus>`, `<duration>` and `<(personal|enterprise|both)>` with the desired values:
+```shell
+act workflow_dispatch -j k6-performance -s GITHUB_TOKEN=`gh auth token` \
+--container-architecture linux/amd64 --artifact-server-path $HOME/.act \ 
+--input vus=<vus> --input duration=<duration> \ 
+--input testSuitePath=<path-to-testscript> \ 
+--input tokens=<(personal|enterprise|both)>
+```
+
+Example of command:
+```shell
+act workflow_dispatch -j k6-performance -s GITHUB_TOKEN=`gh auth token` \
+--container-architecture linux/amd64 --artifact-server-path $HOME/.act \ 
+--input vus=10 --input duration=5m \ 
+--input testSuitePath=tests/k6/tests/serviceowner/performance/create-dialog.js \ 
+--input tokens=enterprise
+```
+
+#### Clean up
+To clean up after the performance test, you can use the `purge-dialogs.js` test file. This file is specifically designed for cleanup purposes. It ensures that any resources created during the test, such as dialogs, are removed from the system.
+
+To run the cleanup script, follow these steps:
+
+1. Navigate to the following directory:
+```shell
+cd tests/k6/tests/serviceowner/performance
+```
+
+2. Run the cleanup script using the following command:
+```shell
+k6 run purge-dialogs.js -e API_VERSION=v1 \
+-e API_ENVIRONMENT=<(test|staging|yt01)>
+```
+
+Replace `<(test|staging|yt01)>` with the appropriate environment where the test was executed.
+
+This script will remove any dialogs created during the performance test, ensuring a clean state for future tests.
+
+### Test Results
+The test results can be found in the GitHub Actions run log and in AppInsights. Currently, the results are exported to a private Grafana instance. Refer to the `.secrets` file mentioned earlier for more details.
+
+### TODO
+- Fix reporting