Przejdź do treści
Biblioteka skilli
Programowanie · Testowanie

woo-testing

/woo-testing

Testuje rozszerzenia WooCommerce: testy jednostkowe i integracyjne PHPUnit, zestaw testów WP, pomocnicze klasy WooCommerce, E2E z Playwright i szkielety testów WP-CLI.

Licencja
MIT
Ostatnia zmiana repozytorium
14.09.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 14.09.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Testuje rozszerzenia WooCommerce: testy jednostkowe i integracyjne PHPUnit, zestaw testów WP, pomocnicze klasy WooCommerce, E2E z Playwright i szkielety testów WP-CLI.

Oryginalny opis (EN)

Test WooCommerce extensions — PHPUnit unit/integration tests, WP test suite, WooCommerce test helpers, E2E with Playwright, and WP-CLI test scaffolding. Use when writing tests for WooCommerce plugins or setting up a test environment.

Jak działa

  1. Before writing code
  2. Test Types
  3. Setting Up PHPUnit Tests
  4. Test Helpers
  5. Testing Patterns
  6. E2E Testing with Playwright
  7. Best Practices
Sekcje z nagłówków SKILL.md, w oryginale · 156 linii, 625 słów
Podgląd SKILL.md
---
name: woo-testing
description: Test WooCommerce extensions — PHPUnit unit/integration tests, WP test suite, WooCommerce test helpers, E2E with Playwright, and WP-CLI test scaffolding. Use when writing tests for WooCommerce plugins or setting up a test environment.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch
---

# WooCommerce Testing

## Before writing code

**Fetch live docs**:
1. Web-search `site:developer.woocommerce.com testing` for WooCommerce testing guide
2. Web-search `site:developer.wordpress.org plugins testing` for WordPress Plugin testing handbook
3. Web-search `woocommerce e2e testing playwright` for E2E patterns

## Test Types

### Unit Tests

Isolated class/function testing:
- No WordPress/WooCommerce bootstrap
- Mock all dependencies
- Fast execution
- Test pure business logic

### Integration Tests

Tests with WordPress + WooCommerce loaded:
- Extend `WC_Unit_Test_Case` (which extends `WP_UnitTestCase`)
- Full WordPress database (using transactions for rollback)
- Access to all WooCommerce APIs and hooks
- Test plugin integration with WooCommerce

### E2E (End-to-End) Tests

Browser-based tests with Playwright:
- Test complete user flows (add to cart, checkout, payment)
- WooCommerce provides Playwright utilities
- Run against a real WordPress + WooCommerce instance

## Setting Up PHPUnit Tests

### Scaffold with WP-CLI

`wp scaffold plugin-tests my-plugin` creates:
- `tests/bootstrap.php` — test bootstrap
- `tests/test-sample.php` — sample test
- `phpunit.xml.dist` — PHPUnit configuration
- `bin/install-wp-tests.sh` — install WordPress test suite

### WooCommerce Test Bootstrap

After WordPress test bootstrap, load WooCommerce and your plugin:
```php
// In tests/bootstrap.php
require_once dirname( __DIR__ ) . '/vendor/woocommerce/woocommerce/tests/legacy/bootstrap.php';
// Or manually: activate WooCommerce, then your plugin
```

### WC_Unit_Test_Case

Base class providing:
- Transaction-based test isolation (each test rolled back)
- WooCommerce helper methods
- Proper environment setup/teardown

## Test Helpers

### WC_Helper_Product

Factory for creating test products:
- `WC_Helper_Product::create_simple_product()` — simple product with defaults
- `WC_Helper_Product::create_variation_product()` — variable + variations
- `WC_Helper_Product::create_grouped_product()` — grouped product
- `WC_Helper_Product::create_external_product()` — external/affiliate

### WC_Helper_Order

Factory for creating test orders:
- `WC_Helper_Order::create_order( $customer_id )` — order with line items
- Configurable status, products, addresses

### WC_Helper_Customer

- `WC_Helper_Customer::create_customer()` — customer with address
- `WC_Helper_Customer::create_mock_customer()` — mock customer object

### WC_Helper_Shipping

- `WC_Helper_Shipping::create_simple_flat_rate()` — flat rate shipping zone
- Set up shipping zones and methods for checkout tests

### WC_Helper_Coupon

- `WC_Helper_Coupon::create_coupon()` — discount coupon with configurable type/amount

## Testing Patterns

### Testing Hooks

Verify your hooks fire correctly:
- Check that a callback is registered: `has_action( 'hook_name', [ $instance, 'method' ] )`
- Test the callback's effect by triggering the hook
- Use `did_action( 'hook_name' )` to verify an action fired

### Testing CRUD Operations

1. Create an object (product, order, etc.)
2. Perform operations (update, delete, query)
3. Assert expected state
4. Cleanup happens automatically via transaction rollback

### Testing REST API Endpoints

Use `WP_REST_Server` to dispatch requests:
- `$request = new WP_REST_Request( 'GET', '/wc/v3/products' )`
- `$response = rest_get_server()->dispatch( $request )`
- Assert status code, response data, headers

### Testing Payment Gateways

- Create order, set payment method
- Call `process_payment()` with test credentials
- Assert order status changes
- Test refund flow

### Mocking

- Use PHPUnit mocks: `$this->createMock( ClassName::class )`
- Mock HTTP requests: `add_filter( 'pre_http_request', $mock_response )`
- WooCommerce provides `WC_Mock_Payment_Gateway` and similar mocks

## E2E Testing with Playwright

### Setup

WooCommerce uses `@woocommerce/e2e-utils` and Playwright:
- Configure in `playwright.config.js`
- Tests in `tests/e2e/specs/`
- Page objects for common pages (shop, cart, checkout, my-account)

### Common E2E Flows

- Add product to cart → verify cart → proceed to checkout → complete order
- Customer registration and login
- Admin: create product, manage orders, configure settings
- Payment gateway integration testing

## Best Practices

- Use `WC_Unit_Test_Case` for integration tests
- Use WooCommerce helper classes (`WC_Helper_Product`, etc.) for test fixtures
- Test with HPOS enabled and disabled
- Test with both classic and block checkout
- Mock external API calls (payment processors, shipping carriers)
- Use `@group` annotations for test organization
- Clean up created data (helpers handle this via transaction rollback)
- Run tests in CI with WordPress test suite

Fetch the WooCommerce testing documentation and WordPress testing handbook for exact helper methods, bootstrap setup, and E2E configuration before implementing.

Wersje

W bazie nie ma innych skilli o nazwie woo-testing.

Migawka bazy z 13.11.2026 · wersja paczki aac941d518b8 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100wp-test-strategy
    Pomaga zaplanować testy WordPressa: PHPUnit, testy integracyjne i end-to-end w Playwright oraz pokrycie WooCommerce.
  • 100php-testing
    Pomaga pisać testy PHP z PHPUnit: testy jednostkowe, mockowanie, data providers, asercje, test doubles i TDD, dla rozszerzeń WooCommerce i projektów PHP.
  • 100woo-setup
    Instaluje WooCommerce, konfiguruje stos deweloperski i lokalne środowisko z WP-CLI, Dockerem lub wp-env przy nowym projekcie WooCommerce.
  • 100php-testing
    Pomaga pisać testy jednostkowe i integracyjne aplikacji PHP z PHPUnit i Pest.
  • 100ns-backend-tests
    Pisze testy jednostkowe i integracyjne PHPUnit w backendzie Laravel, uruchamiane w Dockerze.
  • 90php-testing-patterns
    Pomaga pisać i przeglądać testy PHP w PHPUnit, z narzędziami testowymi WordPressa, WooCommerce i izolacją przez Brain Monkey.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.