Adobe Developer
Commerce
Commerce
PHP Extensions Architecture Development Best Practices Module Reference Coding Standards Tutorials
Console

Edit ProfileSign out
  • Introduction
    • Developer roadmap
    • Composer
    • Common terms
    • Backward-incompatible changes
      • Highlights
      • Reference
  • Prepare
    • Component types
    • Component file structure
    • Extension repository structure
    • Component development roadmap
    • Extension lifecycle
  • Build
    • Dependency injection configuration
    • Optimal development environment
    • Composer integration
    • Required configuration files
    • Create component file structure
    • Register a component
    • URN schema validation
    • Name a component
    • Component load order
    • Enable/disable a component
  • Package
    • Package a component
    • Distribute a component
  • Validate
    • Test a component
  • Partial caching
    • Create custom cache engines
    • Create a cache type
  • Full page caching
    • Public content
    • Private content
  • CLI commands
    • Naming guidelines
    • Create a custom command
  • Staging
  • Advanced reporting
    • Modules
    • Data collection
    • Report XML
  • Component development
    • GraphQL Application Server compatibility
    • Asynchronous and deferred operations
    • Service contracts
      • Design patterns
    • Public interfaces and APIs
    • Dependency injection
    • Object manager
      • Object manager helper
    • Events and observers
      • List of events
    • Factories
    • Proxies
    • Code generation
    • EAV and extension attributes
    • Plugins (interceptors)
    • Routing
    • Indexing
      • Indexer optimization
      • Create a custom indexer
    • Declarative schema
      • Migration scripts
      • Configuration
      • Data and schema patches
    • Web APIs
      • Configure services as web APIs
      • Set custom routes
      • Request processor pool
      • Inventory Management API reference
    • Message queues
      • Asynchronous configuration
      • Topics in asynchronous API
      • Bulk operations
      • Example bulk operation implementation
      • Configure message queues
      • Handling outdated in-memory object states
      • Requests for specific stores
      • Migrate configuration
    • Add extension attributes to entities
    • Add an admin grid
    • Price adjustments
    • Searching with repositories
    • Directory and cache clearing
    • Adapters
    • View models
    • Variable pool
    • Extend catalog rule conditions
  • Payment Provider Gateway
    • Commerce payment provider gateway
      • Payment provider gateway structure
      • Gateway command
      • Gateway command pool
      • Request Builder
      • Gateway client
      • Response Validator
      • Response handler
      • Error code mapping
    • Adding a new payment integration (payment method)
      • Payment method module configuration
      • Payment method configuration
      • Payment method facade
      • Payment info rendering in Admin checkout
      • Add a payment action
      • Get payment information from frontend to backend
      • Configure payment method by area
    • Adding vault integration
      • Add vault to module dependencies
      • Vault payment configuration
      • Vault DI configuration
      • Enable vault
      • Payment token
      • Token UI component provider
      • Display the stored information
      • Vault implementation for Admin
    • CardinalCommerce 3-D Secure
  • Configuration
    • Importers
    • Sensitive and environment-specific settings
  • Framework
    • Array manager
    • DateTime library
    • Float comparator
    • Inventory Management
      • Reservations
      • Source selection algorithms
    • Serialize library
    • Math random
    • URL library
  • Security
    • Authorization
    • Brute force attacks
    • Content security policies
    • Cross-site request forgery
    • Cross-site scripting
    • Data re-encryption
    • Denial of service (DoS) attacks
    • File uploads
    • Mass assignment
    • Non-secure functions
    • Sensitive information
    • Server-side request forgery prevention
    • Subresource Integrity
  • Versioning
    • Check the application version
    • Code changes
    • Dependencies
    • MFTF and backward compatibility
  • Products
  • Commerce
  • Development
  • Validate
Edit in GitHubLog an issue

Validate

After your module is built, you need to test it. Read through the Definition of Done to confirm that your module and coding practice is compliant with Magento.

  • Definition of done in the Contributor Guide.
  • Coding Standards
  • Testing
Distribute a component
Test a component
Dima ShevtsovJeff Matthews
Last updated 9/8/2023
Was this helpful?
Yes
No

APIs and Services

  • Adobe Creative Cloud
  • Adobe Experience Platform
  • Adobe Document Cloud
  • Adobe Cloud Manager
  • Adobe Analytics
  • App Builder
  • View all APIs and ServicesView all

Community

  • Adobe Tech Blog
  • Adobe on GitHub
  • Adobe Developer on YouTube
  • Adobe Developer on X
  • Community Forums

Support

  • Adobe Developer support
  • Adobe Product support

Adobe Developer

  • Adobe Developer Console
  • Developer Distribution
  • Open source at Adobe
  • Download SDKs
  • Authentication
  • Careers
  • Compliance

  • Privacy
  • Terms of Use
  • Cookie preferences
  • Do not sell or share my personal information
  • AdChoices
Copyright © 2025 Adobe. All rights reserved.