12-amaliy mashg‘ulot · 12-mavzu · 2 soat · Korxona ilovalarini dasturlash
Jamoa loyihasi (OmborPro) bosqichi, 5 ta amaliy PHP topshiriq va 3 ta ma’ruzadagi mashq. Yo‘riqnoma bo‘yicha loyihada ishlang, havolani topshiring va PHP topshiriqlarni yeching — server yashirin testlar bilan tekshiradi, o‘qituvchi baho qo‘yadi.
tests/Pest.php va qamrov o‘lchash (PCOV) muhitiniomborpro_test · phpunit.xml · tests/Pest.php · StockService va OrderStatus testlari
Avval alohida test bazasini yarating: docker compose exec db createdb -U omborpro omborpro_test (foydalanuvchi nomi 2-mavzudagi .env ga mos). phpunit.xml dagi <php> bo‘limida DB_CONNECTION=pgsql, DB_DATABASE=omborpro_test, CACHE_STORE=array, QUEUE_CONNECTION=sync, MAIL_MAILER=array qiymatlarini o‘rnating — testlar hech qachon ishchi bazaga yoki real pochtaga tegmasin. tests/Pest.php da uses(TestCase::class, RefreshDatabase::class)->in('Feature') va umumiy yordamchi validOrderPayload() funksiyasini yozing.
Biznes-qoidalar ro‘yxatini 4-mavzudagi invariantlardan oling va har biriga kamida bitta test yozing: OrderStatus — barcha ruxsat etilgan va taqiqlangan o‘tishlar (dataset); StockService::reserve — yetarli qoldiqda rezerv va reserve harakati, yetarli bo‘lmaganda istisno va o‘zgarishsiz holat; ship — quantity va reserved kamayadi, out harakati yoziladi; cancel — rezerv bo‘shatiladi; hisob-faktura — QQS 12 % va chegaraviy yaxlitlash.
Har bir test nomi biznes tilida bo‘lsin va o‘qituvchi test ro‘yxatidan (php artisan test --list-tests yoki chiqish) tizim qoidalarini tushuna olsin. Testlarni yozishda avval testni qizil holatda ko‘ring (masalan, invariantni vaqtincha buzib), keyin yashilga qaytaring — bu testning haqiqatan nimanidir tekshirayotganini isbotlaydi. Kod ichidagi jamoangizga xos metod nomlari (masalan, reserve() parametrlari) slayddagilardan farq qilsa, o‘zingiznikiga moslang.
<php>
<env name="APP_ENV" value="testing"/>
<env name="BCRYPT_ROUNDS" value="4"/>
<env name="DB_CONNECTION" value="pgsql"/>
<env name="DB_DATABASE" value="omborpro_test"/>
<env name="CACHE_STORE" value="array"/>
<env name="QUEUE_CONNECTION" value="sync"/>
<env name="MAIL_MAILER" value="array"/>
<env name="SESSION_DRIVER" value="array"/>
</php>$ docker compose exec db createdb -U omborpro omborpro_test $ docker compose exec app php artisan test Tests: 46 passed (131 assertions) Duration: 3.82s
CACHE_STORE=array — har test toza kesh bilanMAIL_MAILER=array — xatlar hech qayerga ketmaydiBCRYPT_ROUNDS=4 — parol xeshlash tezlashadi — testlar tezroquse Illuminate\Foundation\Testing\RefreshDatabase; use Tests\TestCase; uses(TestCase::class, RefreshDatabase::class)->in('Feature'); function validOrderPayload(array $override = []): array { $product = Product::factory()->create(['price' => '100000.00']); $stock = Stock::factory()->for($product) ->create(['quantity' => 50]); return array_replace([ 'counterparty_id' => Counterparty::factory()->create()->id, 'warehouse_id' => $stock->warehouse_id, 'items' => [['product_id' => $product->id, 'quantity' => 2]], ], $override); }
validOrderPayload(['items' => []]) → ['counterparty_id' => 12, 'warehouse_id' => 3, 'items' => []]
->in('Feature') — Feature testlar Laravel TestCase va toza baza bilanvalidOrderPayload() — har test o‘z ma’lumotini yaratadi — bog‘liqlik yo‘qbeforeEach(function () { $this->stock = Stock::factory()->create([ 'quantity' => 10, 'reserved' => 4, ]); }); it('jo‘natish quantity va reserved ni kamaytiradi', function () { $s = $this->stock; app(StockService::class)->ship($s->warehouse_id, $s->product_id, 4); expect($s->fresh()) ->quantity->toBe(6) ->reserved->toBe(0); $this->assertDatabaseHas('stock_movements', [ 'product_id' => $s->product_id, 'type' => 'out', 'quantity' => 4, ]); });
PASS Tests\Feature\StockServiceTest ✓ it jo‘natish quantity va reserved ni kamaytiradi 0.07s
->quantity->toBe(6) — Pest higher-order tasdiqlari: xossalar zanjiri'type' => 'out' — har bir qoldiq o‘zgarishi jurnalga yoziladi — invariantOrderApiTest · 201/401/403/422 · rollar matritsasi · PCOV · --min
tests/Feature/Api/OrderApiTest.php faylida 7-mavzudagi buyurtmalar API si uchun kamida quyidagilarni yozing: menejer buyurtma yaratadi (201, data.status = draft, order_items da qatorlar); tokensiz so‘rov — 401; rollar matritsasi dataset bilan (admin, menejer — 201; omborchi, buxgalter — 403); validatsiya — bo‘sh items, mavjud bo‘lmagan product_id, manfiy miqdor — 422 va aniq maydon; mass assignment — yaratishda status => 'shipped' yuborilsa ham buyurtma draft. Mahsulotlar ro‘yxati uchun sahifalash va JSON tuzilmasi testi.
Qamrov uchun dev obraziga PCOV qo‘shing (pecl install pcov && docker-php-ext-enable pcov) va php artisan test --coverage --min=70 ni ishga tushiring. Natijadagi eng past foizli servis fayllarini toping va ular uchun test qo‘shing: maqsad — app/Services da kamida 85 %, jami kamida 70 %. HTML hisobotni (--coverage-html coverage) ochib, qizil qatorlar qaysi tarmoqlar ekanini ko‘ring — odatda bular xato holatlari. coverage/ papkasini .gitignore ga qo‘shing.
Composer skriptlari bilan buyruqlarni standartlashtiring: composer test — testlar, composer test:cov — qamrov bilan, composer lint — Pint va Larastan. Shunda har bir jamoa a’zosi va keyinchalik CI bir xil buyruqlarni ishlatadi. Natijalarni (testlar soni, qamrov foizi) README ga yozing.
it('menejer buyurtma yaratadi', function () { $manager = User::factory()->create()->assignRole('menejer'); $this->actingAs($manager, 'api') ->postJson('/api/v1/orders', validOrderPayload([ 'status' => 'shipped', // e’tiborsiz qolishi kerak ])) ->assertCreated() ->assertJsonPath('data.status', 'draft'); $this->assertDatabaseCount('order_items', 1); }); it('tokensiz so‘rov 401', function () { $this->postJson('/api/v1/orders', [])->assertUnauthorized(); });
✓ it menejer buyurtma yaratadi 0.18s ✓ it tokensiz so‘rov 401 0.02s
'status' => 'shipped' — mass assignment hujumi — holat draft qolishi shartassertCreated() — 201 — yangi resurs{
"scripts": {
"test": "pest --parallel",
"test:cov": "pest --coverage --min=70",
"lint": [
"pint --test",
"phpstan analyse --no-progress --memory-limit=1G"
],
"hooks": "git config core.hooksPath .githooks"
}
}$ composer test:cov Services/OrderService ............................ 91.3 % Services/StockService ............................ 96.0 % Total: 78.4 %
"test:cov" — chegaradan past — chiqish kodi xato| Qism | Minimal talab | Tekshiruv |
|---|---|---|
app/Services | ≥ 85 % qamrov | --coverage hisoboti |
| Jami loyiha | ≥ 70 % qamrov | composer test:cov yashil |
| Holat o‘tishlari | Barcha ruxsat va taqiqlar dataset da | Unit test |
| Qoldiq invariantlari | reserve, ship, cancel + yetmaslik holati | Integratsion test |
| Buyurtmalar API | 201, 401, 403 (matritsa), 422 (3 holat) | Feature test |
| Arxitektura | Controllerlarda DB yo‘q, dd() yo‘q | Arch test |
.githooks · PR shabloni · branch himoyasi · jamoaviy review
Ma’ruzadagi .githooks/pre-commit skriptini loyihaga qo‘shing, chmod +x qiling va composer hooks bilan ulang. Docker ichida ishlayotgan bo‘lsangiz, skriptdagi buyruqlarni docker compose exec -T app ./vendor/bin/pint ... ko‘rinishiga o‘zgartiring. Tekshiring: faylga ataylab ortiqcha use qo‘shib commit qiling — hook commitni to‘xtatishi kerak; ./vendor/bin/pint dan keyin commit o‘tadi.
.github/pull_request_template.md faylida PR shablonini yarating: nima o‘zgardi va nima uchun, bog‘langan issue, qanday tekshirildi (testlar, qamrov, skrinshot), ko‘rib chiquvchi uchun tekshiruv ro‘yxati (biznes-qoidalar, tranzaksiya, Policy/validatsiya, N+1, migratsiya). GitHub repozitoriy sozlamalarida main uchun branch himoyasini yoqing: PR orqali merge, kamida 1 tasdiq, yangi commitdan keyin eski tasdiqlarni bekor qilish.
Jamoaviy kod tahlili: har bir a’zo bugungi testlarini alohida PR qilib ochadi va boshqa a’zoning PR ini ko‘rib chiqadi. Kamida 3 ta mazmunli izoh qoldiring (blocking:, question: yoki nit: belgisi bilan), ulardan biri “suggested change” bo‘lsin. Muallif har bir izohga javob beradi yoki tuzatadi, keyin approve va squash merge. O‘qituvchi PR tarixidan izohlar sifati va javoblarni baholaydi.
mkdir -p .githooks cp docs/pre-commit.sh .githooks/pre-commit chmod +x .githooks/pre-commit composer hooks # git config core.hooksPath .githooks # sinov: ataylab uslub xatosi echo "<?php use Foo\Bar;" > app/Tmp.php git add app/Tmp.php && git commit -m "hook sinovi" rm app/Tmp.php && git restore --staged app/Tmp.php
Pint... ⨯ app/Tmp.php no_unused_imports, blank_line_after_opening_tag Uslub xatosi: ./vendor/bin/pint ni ishga tushiring (commit bekor qilindi)
## Nima o‘zgardi va nima uchun Closes # ## Qanday tekshirildi - [ ] Yangi qoida uchun Pest testlari bor - [ ] `composer test:cov` yashil (qamrov pasaymadi) - [ ] `composer lint` xatosiz ## Ko‘rib chiquvchi uchun - [ ] Biznes-qoidalar va invariantlar (qoldiq, holatlar) - [ ] Tranzaksiya, `lockForUpdate`, `afterCommit` - [ ] Policy va validatsiya, `$fillable` - [ ] N+1 yo‘q, kerakli indekslar bor - [ ] Migratsiya qaytariladigan
GitHub: har bir yangi PR tavsifi shu shablon bilan ochiladi
main uchun himoya qoidasini (ruleset) qo‘shishNatija: loyiha biznes-qoidalari va API si Pest testlari bilan himoyalangan, qamrov o‘lchanadi va belgilangan chegaradan past emas, pre-commit hook uslub va tur xatolarini commitdan oldin ushlaydi, o‘zgarishlar Pull Request orqali kod tahlilidan o‘tadi.
Baholash mezonlariomborpro_test PostgreSQL bazasida; RefreshDatabase ulangan; php artisan test yashil.OrderStatus uchun barcha ruxsat etilgan va taqiqlangan o‘tishlar dataset bilan testlangan.StockService uchun reserve, ship, cancel va qoldiq yetmasligi (holat o‘zgarmasligi bilan) testlari bor.app/Services ≥ 85 %, jami ≥ 70 % — composer test:cov natijasi README da..githooks/pre-commit Pint, Larastan va unit testlarni ishlatadi; composer hooks bilan ulanadi.main uchun branch himoyasi sozlangan.📤 Squash merge qilingan Pull Request havolasini yuboring (testlar, hook va shablon bilan); PR da qamrov natijasi, ko‘rib chiquvchi izohlari va ularga javoblar ko‘rinib tursin.
Qanday ishlaydi. Chapdan topshiriqni tanlang, shartni o‘qing va shartdagi imzo bo‘yicha sof PHP funksiya yoki sinf yozing (Laravelsiz). ▶ Sinab ko‘rish — pastdagi chaqiruv ifodasini kodingiz bilan bajaradi (baholanmaydi). ✓ Topshirish — server kodni namunaviy va yashirin testlar bilan tekshiradi; natija o‘qituvchiga ko‘rinadi.