-
Notifications
You must be signed in to change notification settings - Fork 2
52 lines (43 loc) · 1.58 KB
/
k6_cloud.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
# This is a basic workflow to help you get started with Actions
name: k6 Cloud Load Test
# Controls when the workflow will run
on:
# Triggers the workflow on push or pull request events but only for the main branch
push:
branches: [ main ]
pull_request:
branches: [ main ]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "k6_load_test"
k6_load_test:
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- name: Checkout
uses: actions/checkout@v3
- name: Linter, Unit Test, and prebuild step my Fake App
shell: bash
run: |
echo "Test Prebuild Step"
- name: Build my Fake App
shell: bash
run: |
echo "Build Step"
- name: Test Functional and postbuild step my Fake App
shell: bash
run: |
echo "Test Postbuild Step"
- name: Run Test
uses: grafana/k6-action@v0.2.0
with:
cloud: true
filename: $GITHUB_WORKSPACE/testing_en_chile/load_testing_cicd_k6/k6-example-woocommerce/main.js
flags: -v -q # verbose, quiet
token: ${{ secrets.K6_CLOUD_TOKEN }}
env:
K6_CLOUD_PROJECT_ID: ${{ secrets.K6_CLOUD_PROJECT_ID }}