CircleCI
Tento navod vysvetluje, ako integrovat LoadFocus JMeter API klienta s CircleCI na automatizovane testovanie vykonnosti.
Kroky nastavenia
1. Pridanie premennych prostredia
Ulozte vase poverenia LoadFocus API ako premenne prostredia v CircleCI:
- Prejdite na vas projekt v CircleCI
- Prejdite na Project Settings > Environment Variables
- Pridajte nasledujuce premenne:
LOADFOCUS_API_KEY: Vas LoadFocus API klucLOADFOCUS_TEAM_ID: Vase LoadFocus team ID
2. Konfiguracia CircleCI workflow
Vytvorte alebo aktualizujte vas subor .circleci/config.yml na zahrnutie testovania vykonnosti:
version: 2.1jobs:performance_test:docker:- image: cimg/node:16.13steps:- checkout- run:name: Install LoadFocus JMeter API Clientcommand: npm install -g @loadfocus/loadfocus-api-client- run:name: Configure LoadFocus API Clientcommand: |loadfocus-api config set apikey $LOADFOCUS_API_KEYloadfocus-api config set teamid $LOADFOCUS_TEAM_ID- run:name: Run Performance Testscommand: |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.jsondestination: performance-test-resultsworkflows:version: 2build_test_deploy:jobs:- build_and_test- performance_test:requires:- build_and_test- deploy:requires:- performance_testfilters:branches:only: main
3. Zlyhanie buildu pri problemoch s vykonnostou
Aby vas pipeline zlyhal, ked nie su splnene prahy vykonnosti, upravte krok "Run Performance Tests":
- run:name: Run Performance Testscommand: |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 metif [ $? -ne 0 ]; thenecho "Performance test failed to meet thresholds"exit 1fi
Pokrocila konfiguracia
Paralelne testovanie
Na spustenie viacerych testov vykonnosti paralelne:
performance_tests:docker:- image: cimg/node:16.13parallelism: 3steps:- checkout- run:name: Install LoadFocus JMeter API Clientcommand: npm install -g @loadfocus/loadfocus-api-client- run:name: Configure LoadFocus API Clientcommand: |loadfocus-api config set apikey $LOADFOCUS_API_KEYloadfocus-api config set teamid $LOADFOCUS_TEAM_ID- run:name: Run Performance Testscommand: |# Get test name based on indexTESTS=("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_*.jsondestination: performance-test-results
Tipy pre integraciu CircleCI
Alokovanie zdrojov: Zabezpecte, ze vas plan CircleCI ma dostatocne zdroje na spustenie testov vykonnosti, obzvlast ak su dlhotrvajuce.
Nastavenia casoveho limitu: Pre dlhsie testy upravte casovy limit ulohy v CircleCI:
- run:name: Run Performance Testscommand: loadfocus-api jmeter run-test --name "Test_Name" --waitTimeout 3600no_output_timeout: 60mPodmienene testovanie: Spustajte testy vykonnosti iba na konkretnych vetvach alebo pre konkretne commity:
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 >>Notifikacie: Nastavte notifikacie pre zlyhania testov vykonnosti:
- run:name: Notify on Performance Test Failurecommand: |if [ $? -ne 0 ]; thencurl -X POST -H "Content-Type: application/json" \-d '{"text":"Performance test failed for $CIRCLE_PROJECT_REPONAME"}' \$SLACK_WEBHOOK_URLfiwhen: on_fail
Pre viac informacii pozrite dokumentaciu CircleCI a dokumentaciu LoadFocus API klienta.