Replace k6-action with setup-k6-action and run-k6-action

[hggutvik]

Description

• Adds the grafana/setup-k6-action step after the checkout step in all relevant workflows
• Replace all uses of grafana/k6-action with grafana/run-k6-action
  • Only change required is replacing parameter filename with path

Related Issue(s)

• https://github.com/Altinn/team-core-private/issues/266

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Summary by CodeRabbit

• Chores
  • Updated K6 testing infrastructure across CI workflows to use the current test runner integration
  • Added a dedicated K6 initialization step before test execution for more reliable runs
  • Switched test invocation configuration to use path-based references instead of filename keys
  • Applied these standardized changes across multiple test workflows and scenarios

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two GitHub Actions workflow files updated to add a grafana/setup-k6-action setup step, replace usages of grafana/k6-action with grafana/run-k6-action, and change K6 test inputs from filename to path.

Changes

Cohort / File(s)	Summary
Workflows: K6 action replacement & setup .github/workflows/use-case-ATX.yaml, .github/workflows/use-case-TT02.yaml	Add a new step running grafana/setup-k6-action before test runs; replace three test-run steps that used grafana/k6-action with grafana/run-k6-action; change each test action input key from filename to path.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10–15 minutes

• Check that filename → path updates point to correct test files/paths in both workflows.
• Verify the setup-k6-action step appears before the replaced run-k6-action steps and preserves required environment/flags.
• Confirm no other workflow inputs or conditional logic were unintentionally changed.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: replacing k6-action with setup-k6-action and run-k6-action across multiple workflow files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch devops/replace-k6-action

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f200b3 and 76e7d58.

📒 Files selected for processing (2)

• .github/workflows/use-case-ATX.yaml (1 hunks)
• .github/workflows/use-case-TT02.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/use-case-TT02.yaml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Analyze (csharp, autobuild)
• GitHub Check: Build, test & analyze

🔇 Additional comments (2)

.github/workflows/use-case-ATX.yaml (2)

20-21: Add setup-k6-action in correct position.

The setup step is correctly placed after checkout and before the first k6 test execution, ensuring k6 is installed in the environment.

---

22-36: I'll help you verify the consistency of the k6-action migration across both workflow files. Let me run the verification script to check the claims in the review comment.
<function_calls>

#!/bin/bash

Verify both workflow files contain the setup-k6-action step and use run-k6-action consistently

echo "=== Checking .github/workflows/use-case-ATX.yaml ==="
echo "Setup K6 step:"
rg -A 1 "Set up K6" .github/workflows/use-case-ATX.yaml 2>/dev/null || echo "Pattern not found"

echo -e "\nCount of run-k6-action usages:"
rg "run-k6-action" .github/workflows/use-case-ATX.yaml 2>/dev/null | wc -l

echo -e "\n=== Checking .github/workflows/use-case-TT02.yaml (if it exists) ==="
if [ -f ".github/workflows/use-case-TT02.yaml" ]; then
echo "File exists. Checking Setup K6 step:"
rg -A 1 "Set up K6" .github/workflows/use-case-TT02.yaml 2>/dev/null || echo "Pattern not found"

echo -e "\nCount of run-k6-action usages:"
rg "run-k6-action" .github/workflows/use-case-TT02.yaml 2>/dev/null | wc -l
else
echo "File not found"
fi

echo -e "\n=== Verify all old k6-action references are replaced across workflows ==="
rg 'grafana/k6-action' .github/workflows/ 2>/dev/null | head -20 || echo "No k6-action found (expected - all migrated)"

echo -e "\n=== List all workflow files in .github/workflows ==="
ls -la .github/workflows/*.yaml 2>/dev/null | grep -E 'use-case.*yaml' || echo "No matching files found"


</function_calls>

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud