Testing

Ensure your plugin works correctly before deployment.

Manual Testing Steps

1. Copy Plugin to Plugins Folder

cp -r my-plugin /var/www/pteroca/plugins/

2. Scan for Plugin

docker exec pteroca_web_dev php bin/console pteroca:plugin:scan

3. Check Plugin Info

docker exec pteroca_web_dev php bin/console pteroca:plugin:info my-plugin

Expected output:

Plugin: my-plugin
Display Name: My Awesome Plugin
Version: 1.0.0
Author: Your Name <[email protected]>
Status: DISCOVERED
Capabilities: routes, entities, migrations, ui

4. Run Security Scan

docker exec pteroca_web_dev php bin/console pteroca:plugin:security-scan my-plugin --detailed

Look for:

• ✅ No dangerous functions

• ✅ No eval() usage

• ✅ No shell_exec() usage

• ✅ Secure file operations

5. Enable Plugin

docker exec pteroca_web_dev php bin/console pteroca:plugin:enable my-plugin

Watch for errors during:

• Bootstrap initialization

• Migration execution

• Asset publishing

• Service registration

6. Check Health

docker exec pteroca_web_dev php bin/console pteroca:plugin:health my-plugin --detailed

Verify:

• ✅ All capabilities working

• ✅ Database tables created

• ✅ Services registered

• ✅ Routes loaded

7. Test Functionality

In Browser:

1. Access plugin routes: https://your-domain.com/plugins/my-plugin/

2. Check widgets appear on dashboard

3. Verify admin menu items

4. Test server tabs (if applicable)

5. Check settings configuration page

6. Test forms and CRUD operations

Via CLI:

# Test commands
docker exec pteroca_web_dev php bin/console my-plugin:greet John

# Test cron tasks
docker exec pteroca_web_dev php bin/console pteroca:cron:run my-plugin:cleanup --dry-run

8. Check Logs for Errors

docker exec pteroca_web_dev tail -f var/log/prod.log
docker exec pteroca_web_dev tail -f var/log/dev.log

Look for:

• PHP errors

• SQL errors

• Missing files

• Permission issues

9. Disable and Re-enable

docker exec pteroca_web_dev php bin/console pteroca:plugin:disable my-plugin
docker exec pteroca_web_dev php bin/console pteroca:plugin:enable my-plugin

Verify:

• Cleanup runs properly

• Re-initialization works

• Data persists

• Settings remain

Debugging

Check Logs

# Production logs
docker exec pteroca_web_dev tail -f var/log/prod.log

# Development logs
docker exec pteroca_web_dev tail -f var/log/dev.log

# Follow logs in real-time
docker exec pteroca_web_dev tail -f var/log/dev.log | grep MyPlugin

Verify Autoloading

# Check if classes are found
docker exec pteroca_web_dev php bin/console debug:container | grep MyPlugin

# Specific service
docker exec pteroca_web_dev php bin/console debug:container Plugins\\MyPlugin\\Service\\MyService

Check Routes

# List all plugin routes
docker exec pteroca_web_dev php bin/console debug:router | grep plugin_my_plugin

# Specific route
docker exec pteroca_web_dev php bin/console debug:router plugin_my_plugin_index

Verify Migrations

# Check migration status
docker exec pteroca_web_dev php bin/console doctrine:migrations:status

# List migrations
docker exec pteroca_web_dev php bin/console doctrine:migrations:list

Test Database Queries

# Access MySQL
docker exec -it pteroca_db mysql -u pteroca -p pteroca

# Check tables
SHOW TABLES LIKE 'plg_%';

# Query plugin data
SELECT * FROM plg_my_visit_log LIMIT 10;

Common Issues

Class Not Found

Problem: Class 'Plugins\MyPlugin\Controller\MyController' not found

Solutions:

1. Check namespace matches directory structure (PSR-4)

   Namespace: Plugins\MyPlugin\Controller\MyController
   File: plugins/my-plugin/src/Controller/MyController.php

2. Clear cache: php bin/console cache:clear

3. Verify composer autoloading (if using composer.json)

Routes Not Working

Problem: 404 errors when accessing plugin routes

Solutions:

1. Check route naming convention: plugin_{name}_{action}

2. Verify controller is tagged: controller.service_arguments

3. Clear cache

4. Check routes loaded: debug:router | grep plugin_my_plugin

Assets Not Loading

Problem: CSS/JS files return 404

Solutions:

1. Republish assets:

   docker exec pteroca_web_dev php bin/console pteroca:plugin:assets:publish my-plugin --force

2. Check file permissions

3. Verify asset paths in plugin.json

4. Check symlinks in public/assets/plugins/my-plugin/

Database Errors

Problem: SQL syntax errors or table doesn't exist

Solutions:

1. Check migration SQL syntax

2. Verify table names use plg_ prefix

3. Test migration manually:

   docker exec pteroca_web_dev php bin/console doctrine:migrations:migrate

4. Check database user permissions

Widget Not Appearing

Problem: Widget doesn't show on dashboard

Solutions:

1. Verify widget is tagged: tags: ['widget']

2. Check isVisible() returns true

3. Check context matches: WidgetContext::DASHBOARD

4. Clear cache

5. Check for JavaScript errors in browser console

Settings Not Saving

Problem: Plugin settings don't persist

Solutions:

1. Verify settings context: plugin:my-plugin

2. Check config_schema in plugin.json

3. Verify database table setting exists

4. Check user permissions

Browser Testing

Check JavaScript Console

1. Open browser DevTools (F12)

2. Go to Console tab

3. Look for errors when:

   • Loading pages

   • Clicking buttons

   • Submitting forms

Check Network Tab

1. Go to Network tab in DevTools

2. Verify:

   • Assets load successfully (200 status)

   • API calls return correct responses

   • No CORS errors

   • Proper content types

Test in Multiple Browsers

• Chrome/Chromium

• Firefox

• Safari (if applicable)

• Edge

Test Responsive Design

• Desktop (1920x1080)

• Tablet (768x1024)

• Mobile (375x667)

Performance Testing

Check Plugin Load Time

# Time command execution
time docker exec pteroca_web_dev php bin/console my-plugin:sync

Monitor Memory Usage

// Add to plugin code
$memoryBefore = memory_get_usage();
// ... operation ...
$memoryAfter = memory_get_usage();
$this->logger->info('Memory used', [
    'bytes' => $memoryAfter - $memoryBefore
]);

Profile Database Queries

Enable Symfony profiler in development and check query count/time.

Automated Testing (Optional)

Unit Tests

<?php
namespace Plugins\MyPlugin\Tests\Unit;

use PHPUnit\Framework\TestCase;
use Plugins\MyPlugin\Service\MyService;

class MyServiceTest extends TestCase
{
    public function testDoSomething(): void
    {
        $service = new MyService();
        $result = $service->doSomething();

        $this->assertEquals('expected', $result);
    }
}

Integration Tests

<?php
namespace Plugins\MyPlugin\Tests\Integration;

use Symfony\Bundle\FrameworkBundle\Test\KernelTestCase;

class DatabaseTest extends KernelTestCase
{
    public function testEntityPersistence(): void
    {
        self::bootKernel();
        $entityManager = self::$kernel->getContainer()
            ->get('doctrine')
            ->getManager();

        // Test database operations
    }
}

Run Tests

docker exec pteroca_web_dev php vendor/bin/phpunit plugins/my-plugin/tests/

Checklist Before Release

• Plugin scans successfully

• Security scan passes

• Plugin enables without errors

• Health check passes

• All routes work

• Assets load correctly

• Database migrations run

• Widgets appear

• Cron tasks execute

• Commands work

• Settings save/load

• No errors in logs

• Works after disable/re-enable

• Translation keys work

• JavaScript has no console errors

• Responsive on mobile

• Tested in multiple browsers

• Documentation complete

• Version number updated

Related Guides

• Best Practices - Code quality guidelines

• Plugin Structure - Verify file organization

• Dependencies - Service debugging