Azure DevOps

Ta vodnik pojasnjuje, kako integrirati odjemalca JMeter API LoadFocus z Azure DevOps za avtomatizirano testiranje zmogljivosti.

Koraki nastavitve

1. Shranjevanje poverilnic v Azure Key Vault

Za varno upravljanje poverilnic shranite poverilnice API LoadFocus v Azure Key Vault:

  1. Ustvarite Key Vault v Azure, če ga še nimate
  2. Dodajte naslednje skrivnosti:
    • loadfocus-api-key: Vaš API ključ LoadFocus
    • loadfocus-team-id: Vaš ID ekipe LoadFocus
  3. Nastavite povezavo storitve za dostop do Key Vault iz vašega cevovoda

2. Ustvarjanje cevovoda Azure

Ustvarite novo datoteko z imenom azure-pipelines.yml v vašem repozitoriju:

trigger:
  - main
  - develop


pool:
  vmImage: 'ubuntu-latest'


variables:
  - group: loadfocus-variables  # Variable group containing Key Vault references


stages:
  - stage: Build
    jobs:
      - job: BuildAndTest
        steps:
          # Your existing build and test steps...


  - stage: PerformanceTest
    dependsOn: Build
    condition: succeeded()
    jobs:
      - job: RunPerformanceTests
        steps:
          - task: NodeTool@0
            inputs:
              versionSpec: '16.x'
            displayName: 'Install Node.js'


          - script: |
              npm install -g @loadfocus/loadfocus-api-client
            displayName: 'Install LoadFocus JMeter API Client'


          - script: |
              loadfocus-api config set apikey $(LOADFOCUS_API_KEY)
              loadfocus-api config set teamid $(LOADFOCUS_TEAM_ID)
            displayName: 'Configure LoadFocus API Client'


          - script: |
              loadfocus-api jmeter run-test \
                --name "AzureDevOps_$(Build.Repository.Name)_$(Build.SourceBranchName)" \
                --thresholds "avgresponse<=200,errors==0,p95<=250" \
                --format json > $(Build.ArtifactStagingDirectory)/performance_results.json
            displayName: 'Run Performance Tests'
            continueOnError: false


          - task: PublishBuildArtifacts@1
            inputs:
              pathtoPublish: '$(Build.ArtifactStagingDirectory)'
              artifactName: 'performance-test-results'
            displayName: 'Publish Performance Test Results'


  - stage: Deploy
    dependsOn: PerformanceTest
    condition: succeeded()
    jobs:
      - job: DeployApplication
        steps:
          # Your deployment steps...

3. Nastavitev skupine spremenljivk z integracijo Key Vault

  1. Pojdite na Pipelines > Library > Variable Groups
  2. Ustvarite novo skupino spremenljivk z imenom "loadfocus-variables"
  3. Povežite jo z vašim Azure Key Vault
  4. Dodajte naslednje spremenljivke in jih povežite s skrivnostmi Key Vault:
    • LOADFOCUS_API_KEY: Povežite s skrivnostjo loadfocus-api-key
    • LOADFOCUS_TEAM_ID: Povežite s skrivnostjo loadfocus-team-id

Napredna konfiguracija

Uporaba predlog YAML

Za ponovno uporabne korake testiranja zmogljivosti ustvarite datoteko predloge performance-test-template.yml:

parameters:
  testName: 'Default_Test'
  thresholds: 'avgresponse<=200,errors==0,p95<=250'
  waitTimeout: 1800


steps:
- script: |
    loadfocus-api jmeter run-test \
      --name "${{ parameters.testName }}" \
      --thresholds "${{ parameters.thresholds }}" \
      --waitTimeout ${{ parameters.waitTimeout }} \
      --format json > $(Build.ArtifactStagingDirectory)/performance_results.json
  displayName: 'Run Performance Tests'
  continueOnError: false

Nato v vašem glavnem cevovodu:

- template: performance-test-template.yml
  parameters:
    testName: 'AzureDevOps_$(Build.Repository.Name)_$(Build.SourceBranchName)'
    thresholds: 'avgresponse<=150,errors==0,p95<=200'
    waitTimeout: 2400

Izvajanje več testov

Za zaporedno izvajanje več testov zmogljivosti:

- script: |
    # Run API test
    loadfocus-api jmeter run-test \
      --name "API_Test" \
      --thresholds "avgresponse<=200,errors==0" \
      --format json > $(Build.ArtifactStagingDirectory)/api_test_results.json


    # Run UI test
    loadfocus-api jmeter run-test \
      --name "UI_Test" \
      --thresholds "avgresponse<=500,errors==0" \
      --format json > $(Build.ArtifactStagingDirectory)/ui_test_results.json
  displayName: 'Run Multiple Performance Tests'

Integracija z Azure Test Plans

Za integracijo rezultatov testov zmogljivosti z Azure Test Plans:

- task: PublishTestResults@2
  inputs:
    testResultsFormat: 'JUnit'
    testResultsFiles: '$(Build.ArtifactStagingDirectory)/test-results.xml'
    testRunTitle: 'Performance Tests'
  displayName: 'Publish Test Results'
  condition: succeededOrFailed()

Izhod JSON boste morali pretvoriti v obliko JUnit:

- script: |
    # Run performance test
    loadfocus-api jmeter run-test \
      --name "AzureDevOps_Test" \
      --thresholds "avgresponse<=200,errors==0" \
      --format json > $(Build.ArtifactStagingDirectory)/performance_results.json


    # Convert JSON to JUnit format (using a custom script)
    node convert-to-junit.js \
      $(Build.ArtifactStagingDirectory)/performance_results.json \
      $(Build.ArtifactStagingDirectory)/test-results.xml
  displayName: 'Run Performance Tests and Convert Results'

Nasveti za integracijo z Azure DevOps

  1. Vzporedna opravila: Če imate več testov zmogljivosti, razmislite o uporabi vzporednih opravil:

    jobs:
    - job: API_Performance_Test
      steps:
        # Run API performance test
    

    - job: UI_Performance_Test
      steps:
        # Run UI performance test

  2. Vrata za uvajanje: Uporabite rezultate testov zmogljivosti kot vrata za uvajanje:

    - job: DeploymentGate
      steps:
      - script: |
          # Check if performance tests passed
          if grep -q '"overallResult": "FAILED"' $(Build.ArtifactStagingDirectory)/performance_results.json; then
            echo "##vso[task.logissue type=error]Performance tests failed"
            echo "##vso[task.complete result=Failed;]"
          fi

  3. Prilagojena nadzorna plošča: Ustvarite prilagojeno nadzorno ploščo za vizualizacijo rezultatov testov zmogljivosti skozi čas.

  4. Obvestila: Nastavite obvestila za neuspehe testov zmogljivosti:

    - task: SendEmail@1
      inputs:
        to: 'team@example.com'
        subject: 'Performance Test Failed'
        body: 'Performance tests failed to meet thresholds. See attached results.'
        addAttachment: true
        attachmentPath: '$(Build.ArtifactStagingDirectory)/performance_results.json'
      condition: failed()

Za več informacij si oglejte dokumentacijo Azure DevOps in dokumentacijo odjemalca API LoadFocus.

Prejšnji
Integracija API za obremenilno testiranje
Naslednji
CircleCI