Algolia

    GitLab CI/CD

    Denne veiledningen forklarer hvordan du integrerer LoadFocus JMeter API-klienten med GitLab CI/CD for automatisert ytelsestesting.

    Oppsettstrinn

    1. Lagre legitimasjon som GitLab CI/CD-variabler

    Først, lagre LoadFocus API-legitimasjonen din som GitLab CI/CD-variabler:

    1. Gå til GitLab-prosjektet ditt
    2. Naviger til Settings > CI/CD > Variables
    3. Legg til følgende variabler:
      • LOADFOCUS_API_KEY: Din LoadFocus API-nøkkel (merk som "Masked")
      • LOADFOCUS_TEAM_ID: Din LoadFocus team-ID

    2. Opprett en GitLab CI/CD Pipeline

    Opprett eller oppdater .gitlab-ci.yml-filen i repositoriet ditt:

    stages:
      - build
      - test
      - performance
      - deploy
    

    variables:
      NODE_VERSION: "16"
    

    build:
      stage: build
      image: node:${NODE_VERSION}
      script:
        - npm install
        - npm run build
      artifacts:
        paths:
          - dist/
        expire_in: 1 week
    

    test:
      stage: test
      image: node:${NODE_VERSION}
      script:
        - npm install
        - npm test
    

    performance_test:
      stage: performance
      image: node:${NODE_VERSION}
      script:
        # Install LoadFocus JMeter API Client
        - npm install -g @loadfocus/loadfocus-api-client
    

        # Configure LoadFocus API Client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
    

        # Run Performance Tests
        - |
          loadfocus-api jmeter run-test \
            --name "GitLab_${CI_PROJECT_NAME}_${CI_COMMIT_REF_NAME}" \
            --thresholds "avgresponse<=200,errors==0,p95<=250" \
            --format json > performance_results.json
      artifacts:
        paths:
          - performance_results.json
        expire_in: 1 week
        when: always
      # Optional: Only run on specific branches
      only:
        - main
        - develop
    

    deploy:
      stage: deploy
      script:
        - echo "Deploying application..."
      only:
        - main
      # Only deploy if all previous stages succeeded
      when: on_success

    3. Vis testresultater

    Etter at pipelinen har kjørt:

    1. Gå til GitLab-prosjektet ditt
    2. Naviger til CI/CD > Pipelines
    3. Finn pipelinen din og klikk på den
    4. Gå til "performance_test"-jobben
    5. Klikk på "Browse" i høyre sidepanel for å se artefakter
    6. Last ned og vis performance_results.json-filen

    Avansert konfigurasjon

    Miljøspesifikk testing

    Kjør forskjellige ytelsestester for forskjellige miljøer:

    .performance_test_template: &performance_test_definition
      stage: performance
      image: node:${NODE_VERSION}
      script:
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "${TEST_NAME}" \
            --thresholds "${THRESHOLDS}" \
            --format json > performance_results.json
      artifacts:
        paths:
          - performance_results.json
        expire_in: 1 week
        when: always
    

    performance_test_develop:
      <<: *performance_test_definition
      variables:
        TEST_NAME: "API_Test_Develop"
        THRESHOLDS: "avgresponse<=300,errors==0,p95<=500"
      only:
        - develop
    

    performance_test_staging:
      <<: *performance_test_definition
      variables:
        TEST_NAME: "API_Test_Staging"
        THRESHOLDS: "avgresponse<=250,errors==0,p95<=350"
      only:
        - staging
    

    performance_test_production:
      <<: *performance_test_definition
      variables:
        TEST_NAME: "API_Test_Production"
        THRESHOLDS: "avgresponse<=200,errors==0,p95<=250"
      only:
        - main

    Parallell testing

    Kjør flere ytelsestester parallelt:

    performance_test_api:
      stage: performance
      image: node:${NODE_VERSION}
      script:
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "API_Performance_Test" \
            --thresholds "avgresponse<=150,errors==0" \
            --format json > api_performance_results.json
      artifacts:
        paths:
          - api_performance_results.json
        expire_in: 1 week
    

    performance_test_ui:
      stage: performance
      image: node:${NODE_VERSION}
      script:
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "UI_Performance_Test" \
            --thresholds "avgresponse<=300,errors==0" \
            --format json > ui_performance_results.json
      artifacts:
        paths:
          - ui_performance_results.json
        expire_in: 1 week

    Deretter opprett en planlagt pipeline i GitLab:

    1. Gå til GitLab-prosjektet ditt
    2. Naviger til CI/CD > Schedules
    3. Klikk "New schedule"
    4. Sett opp en tidsplan (f.eks. hver dag ved midnatt)

    Opprette ytelsesrapporter

    Generer HTML-rapporter fra JSON-resultater:

    performance_test:
      stage: performance
      image: node:${NODE_VERSION}
      script:
        # Run performance test
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "GitLab_${CI_PROJECT_NAME}_${CI_COMMIT_REF_NAME}" \
            --thresholds "avgresponse<=200,errors==0,p95<=250" \
            --format json > performance_results.json
    

        # Generate HTML report
        - npm install -g performance-report-generator  # Replace with actual report generator
        - performance-report-generator --input performance_results.json --output performance_report.html
      artifacts:
        paths:
          - performance_results.json
          - performance_report.html
        expire_in: 1 week
        when: always
      # Optional: Publish report as GitLab Pages
      pages:
        stage: deploy
        dependencies:
          - performance_test
        script:
          - mkdir -p public/performance-reports
          - cp performance_report.html public/performance-reports/index.html
        artifacts:
          paths:
            - public
        only:
          - main

    Integrasjon med GitLab-funksjoner

    Merge Request-widgeter

    Vis ytelsestestresultater i merge requests ved hjelp av GitLabs JUnit-rapportfunksjon:

    performance_test:
      stage: performance
      image: node:${NODE_VERSION}
      script:
        # Run performance test
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "GitLab_${CI_PROJECT_NAME}_${CI_COMMIT_REF_NAME}" \
            --thresholds "avgresponse<=200,errors==0,p95<=250" \
            --format json > performance_results.json
    

        # Convert to JUnit format (using a custom script)
        - node convert-to-junit.js performance_results.json junit-report.xml
      artifacts:
        reports:
          junit: junit-report.xml
        paths:
          - performance_results.json
        expire_in: 1 week

    GitLab Metrics

    Bruk GitLabs metrikkfunksjon for å spore ytelse over tid:

    performance_test:
      stage: performance
      image: node:${NODE_VERSION}
      script:
        # Run performance test
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "GitLab_${CI_PROJECT_NAME}_${CI_COMMIT_REF_NAME}" \
            --thresholds "avgresponse<=200,errors==0,p95<=250" \
            --format json > performance_results.json
    

        # Extract metrics and report them to GitLab
        - |
          # Parse JSON and extract metrics
          RESPONSE_TIME=$(jq '.labels[0].metrics.avgresponse' performance_results.json)
          ERROR_RATE=$(jq '.labels[0].metrics.errors' performance_results.json)
    

          # Report metrics
          echo "performance_avg_response_time ${RESPONSE_TIME}" >> metrics.txt
          echo "performance_error_rate ${ERROR_RATE}" >> metrics.txt
      artifacts:
        reports:
          metrics: metrics.txt
        paths:
          - performance_results.json
        expire_in: 1 week

    GitLab Environments

    Knytt ytelsestester til spesifikke miljøer:

    performance_test_staging:
      stage: performance
      image: node:${NODE_VERSION}
      environment:
        name: staging
      script:
        - npm install -g @loadfocus/loadfocus-api-client
        - loadfocus-api config set apikey $LOADFOCUS_API_KEY
        - loadfocus-api config set teamid $LOADFOCUS_TEAM_ID
        - |
          loadfocus-api jmeter run-test \
            --name "Staging_Performance_Test" \
            --thresholds "avgresponse<=250,errors==0" \
            --format json > performance_results.json
      artifacts:
        paths:
          - performance_results.json
        expire_in: 1 week
      only:
        - staging

    Tips for GitLab CI/CD-integrasjon

    1. Hurtigbufring: Hurtigbufre npm-avhengigheter for å akselerere pipeline-kjøringer:

      performance_test:
        stage: performance
        image: node:${NODE_VERSION}
        cache:
          key: ${CI_COMMIT_REF_SLUG}
          paths:
            - node_modules/
        script:
          - npm install -g @loadfocus/loadfocus-api-client
          # Rest of the script...

    2. Tidsavbruddsinnstillinger: Sett tidsavbrudd for langvarige ytelsestester:

      performance_test:
        stage: performance
        image: node:${NODE_VERSION}
        timeout: 2h  # Set a 2-hour timeout
        script:
          # Performance test script...

    3. Manuelle utløsere: Tillat at ytelsestester utløses manuelt:

      performance_test:
        stage: performance
        image: node:${NODE_VERSION}
        script:
          # Performance test script...
        when: manual

    4. Dynamisk testkonfigurasjon: Bruk GitLab-forhåndsdefinerte variabler for å dynamisk konfigurere tester:

      performance_test:
        stage: performance
        image: node:${NODE_VERSION}
        script:
          - |
            # Set thresholds based on branch
            if [ "$CI_COMMIT_REF_NAME" = "main" ]; then
              THRESHOLDS="avgresponse<=200,errors==0,p95<=250"
            else
              THRESHOLDS="avgresponse<=300,errors==0,p95<=500"
            fi
      

            loadfocus-api jmeter run-test \
              --name "GitLab_${CI_PROJECT_NAME}_${CI_COMMIT_REF_NAME}" \
              --thresholds "$THRESHOLDS" \
              --format json > performance_results.json

    5. Varsler: Send varsler når ytelsestester feiler:

      performance_test:
        stage: performance
        image: node:${NODE_VERSION}
        script:
          # Performance test script...
        after_script:
          - |
            if [ $? -ne 0 ]; then
              # Send notification using curl, GitLab API, or other method
              curl -X POST -H "Content-Type: application/json" \
                -d "{\"text\":\"Performance test failed for ${CI_PROJECT_NAME}\"}" \
                $WEBHOOK_URL
            fi

    For mer informasjon, se GitLab CI/CD-dokumentasjonen og LoadFocus API-klientdokumentasjonen.

    Forrige
    GitHub Actions
    Neste
    Jenkins