CircleCI

Denne guide forklarer, hvordan du integrerer LoadFocus JMeter API Client med CircleCI til automatiseret ydeevnetest.

Opsætningstrin

1. Tilføj miljøvariabler

Gem dine LoadFocus API-legitimationsoplysninger som miljøvariabler i CircleCI:

Naviger til dit projekt i CircleCI
Gå til Project Settings > Environment Variables
Tilføj følgende variabler:
- LOADFOCUS_API_KEY: Din LoadFocus API-nøgle
- LOADFOCUS_TEAM_ID: Dit LoadFocus team-ID

2. Konfigurer CircleCI Workflow

Opret eller opdater din .circleci/config.yml-fil til at inkludere ydeevnetest:

version: 2.1
jobs:
  performance_test:
    docker:
      - image: cimg/node:16.13
    steps:
      - checkout
      - run:
          name: Install LoadFocus JMeter API Client
          command: npm install -g @loadfocus/loadfocus-api-client
      - run:
          name: Configure LoadFocus API Client
          command: |
            loadfocus-api config set apikey $LOADFOCUS_API_KEY
            loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
      - run:
          name: Run Performance Tests
          command: |
            loadfocus-api jmeter run-test \
              --name "CircleCI_${CIRCLE_PROJECT_REPONAME}_${CIRCLE_BRANCH}" \
              --thresholds "avgresponse<=200,errors==0,p95<=250" \
              --format json > performance_results.json
      - store_artifacts:
          path: performance_results.json
          destination: performance-test-results

workflows:
  version: 2
  build_test_deploy:
    jobs:
      - build_and_test
      - performance_test:
          requires:
            - build_and_test
      - deploy:
          requires:
            - performance_test
          filters:
            branches:
              only: main

3. Fejl bygget ved ydeevneproblemer

For at få din pipeline til at fejle, når ydeevnetærskler ikke opfyldes, modificer trinnet "Run Performance Tests":

- run:
    name: Run Performance Tests
    command: |
      loadfocus-api jmeter run-test \
        --name "CircleCI_${CIRCLE_PROJECT_REPONAME}_${CIRCLE_BRANCH}" \
        --thresholds "avgresponse<=200,errors==0,p95<=250" \
        --format json > performance_results.json

      # Check exit code - the command will exit with code 1 if thresholds are not met
      if [ $? -ne 0 ]; then
        echo "Performance test failed to meet thresholds"
        exit 1
      fi

Avanceret konfiguration

Parallel test

For kørsel af flere ydeevnetests parallelt:

performance_tests:
  docker:
    - image: cimg/node:16.13
  parallelism: 3
  steps:
    - checkout
    - run:
        name: Install LoadFocus JMeter API Client
        command: npm install -g @loadfocus/loadfocus-api-client
    - run:
        name: Configure LoadFocus API Client
        command: |
          loadfocus-api config set apikey $LOADFOCUS_API_KEY
          loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
    - run:
        name: Run Performance Tests
        command: |
          # Get test name based on index
          TESTS=("API_Test" "Frontend_Test" "Database_Test")
          INDEX=$(( $CIRCLE_NODE_INDEX % 3 ))
          TEST_NAME=${TESTS[$INDEX]}

          echo "Running test: $TEST_NAME"

          loadfocus-api jmeter run-test \
            --name "$TEST_NAME" \
            --thresholds "avgresponse<=200,errors==0,p95<=250" \
            --format json > "performance_results_${TEST_NAME}.json"
    - store_artifacts:
        path: performance_results_*.json
        destination: performance-test-results

Tips til CircleCI-integration

Ressourceallokering: Sørg for, at din CircleCI-plan har tilstrækkelige ressourcer til at køre ydeevnetests, især hvis de er langvarige.

Timeout-indstillinger: For længere tests, juster job-timeout i CircleCI:

- run:
    name: Run Performance Tests
    command: loadfocus-api jmeter run-test --name "Test_Name" --waitTimeout 3600
    no_output_timeout: 60m

Betinget test: Kør kun ydeevnetests på specifikke branches eller for specifikke commits:

performance_test:
  # Only run if commit message contains [PERF-TEST]
  when:
    condition:
      or:
        - equal: [ main, << pipeline.git.branch >> ]
        - matches:
            pattern: ".*\\[PERF-TEST\\].*"
            value: << pipeline.git.commit.message >>

Notifikationer: Opsæt notifikationer for fejlede ydeevnetests:

- run:
    name: Notify on Performance Test Failure
    command: |
      if [ $? -ne 0 ]; then
        curl -X POST -H "Content-Type: application/json" \
          -d '{"text":"Performance test failed for $CIRCLE_PROJECT_REPONAME"}' \
          $SLACK_WEBHOOK_URL
      fi
    when: on_fail

For mere information, se CircleCI-dokumentationen og LoadFocus API Client-dokumentationen.