CircleCI
Siame vadove paaiskiname, kaip integruoti LoadFocus JMeter API klienta su CircleCI automatizuotam nasumui testuoti.
Nustatymo zingsniai
1. Pridekite aplinkos kintamuosius
Saugokite savo LoadFocus API kredencialus kaip aplinkos kintamuosius CircleCI:
- Eikite i savo projekta CircleCI
- Eikite i Project Settings > Environment Variables
- Pridekite siuos kintamuosius:
LOADFOCUS_API_KEY: jusu LoadFocus API raktasLOADFOCUS_TEAM_ID: jusu LoadFocus komandos ID
2. Sukonfiguruokite CircleCI darbo eiga
Sukurkite arba atnaujinkite savo .circleci/config.yml faila, kad itrauktumete nasumo testavima:
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. Sustabdykite surinkima esant nasumo problemoms
Norint, kad jusu konvejeris nepavyktu, kai nasumo ribines vertes nera pasiektos, modifikuokite "Run Performance Tests" zingsni:
- 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
Isplestine konfiguracija
Lygiagretus testavimas
Keliu nasumo testu vykdymui lygiagredziai:
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
Patarimai CircleCI integracijai
Resursu paskirstymas: isitikinkite, kad jusu CircleCI planas turi pakankamai resursu nasumo testams vykdyti, ypac jei jie trunka ilgai.
Laiko limito nustatymai: ilgesniems testams pakoreguokite uzduoties laiko limita CircleCI:
- run:name: Run Performance Testscommand: loadfocus-api jmeter run-test --name "Test_Name" --waitTimeout 3600no_output_timeout: 60mSalyginis testavimas: vykdykite nasumo testus tik konkreciose sakose arba konkretiems issiuntimams:
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 >>Pranesimai: nustatykite pranesimus apie nasumo testu nesekmes:
- 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
Daugiau informacijos rasite CircleCI dokumentacijoje ir LoadFocus API kliento dokumentacijoje.