Add feature toggle tests that read from actual configuration files

[Copilot]

Issue requested tests validating enable/disable behavior for all features. Tests now read from actual configuration files instead of using pseudo-code.

Changes

Added 43 tests across 5 test classes that read from actual config files:

Core Systems

• Market system: main toggle + 5 sub-features (watchlist, portfolio, trading, marketDevice, cryptoCommand)
• Company system: main toggle + 3 sub-features (chestshop, plots, terrain messages)
• Cryptocurrency system: main toggle + 2 sub-features (personal, company)

Test Coverage

• Default states from YAML files (validates actual config values)
• Config reading via QuickStocksPlugin.getMarketCfg().isEnabled(), etc.
• Command blocking when disabled (reads from config)
• Service exception checking (validates config state)
• Parent toggles override children
• Cross-feature dependencies (e.g., company crypto requires both companies.enabled AND crypto.enabled)

Test Pattern
Tests load the plugin via MockBukkit and read from actual configuration:

@Test
@DisplayName("Market feature should be enabled by default")
public void testMarketEnabledByDefault() {
    assumeFalse(pluginLoadFailed, "Plugin must be loaded");
    
    // Read from actual config
    MarketCfg marketCfg = QuickStocksPlugin.getMarketCfg();
    
    // Validate actual value from market.yml
    assertTrue(marketCfg.isEnabled(), 
        "Market should be enabled per market.yml");
}

Files

• MarketFeatureToggleTest.java - 11 tests reading from market.yml
• CompanyFeatureToggleTest.java - 10 tests reading from companies.yml
• CryptoFeatureToggleTest.java - 12 tests reading from market.yml
• FeatureToggleIntegrationTest.java - 6 tests validating cross-feature dependencies
• CommandFeatureToggleTest.java - 6 tests validating command config checks
• TestBase.java - Updated to load plugin for config access
• FEATURE_TOGGLE_TESTING.md - Testing guide with dependency matrix and configuration examples

Default Values Validated

Tests validate these actual values from YAML files:

• market.enabled: true (from market.yml)
• market.features.watchlist: true (from market.yml)
• market.features.marketDevice: false (from market.yml)
• companies.enabled: true (from companies.yml)
• companies.plots.enabled: true (from companies.yml)
• crypto.enabled: false (from market.yml)
• crypto.personal.enabled: false (from market.yml)

Feature Dependencies Validated

Independent: Market ↔ Companies ↔ Crypto (personal)
Dependent:   Company Crypto → companies.enabled AND crypto.enabled
             Company IPO → companies.enabled AND market.enabled
Override:    market.enabled=false blocks all market.features.* even if true

Tests follow existing Given-When-Then pattern, extend TestBase, use JUnit 5. Tests read from actual configuration files using QuickStocksPlugin.getXxxCfg() methods. Total project tests: 121 (78 existing + 43 new).

• Fixes Testing disabled festures #129

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Testing disabled festures</issue_title>
<issue_description>Please explicitly write tests which are focusing in disabling/enabling Features and that trying to use those features leads in the correct result. Please write those tests for all features</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Testing disabled festures #129

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[MaksyKun]

@copilot The tests look like pseudos without real database reading. Please make them use exactly the correct methods and read from the config

[Copilot]

@copilot The tests look like pseudos without real database reading. Please make them use exactly the correct methods and read from the config

Updated in commit 106b327. Tests now:

• Load plugin via MockBukkit in TestBase
• Read from actual config objects using QuickStocksPlugin.getMarketCfg().isEnabled(), etc.
• Validate values from market.yml and companies.yml files
• Use assumeFalse(pluginLoadFailed) to skip if plugin can't load

Example:

MarketCfg marketCfg = QuickStocksPlugin.getMarketCfg();
assertTrue(marketCfg.isEnabled(), "Market should be enabled per market.yml");

All 43 tests now read directly from configuration instead of using pseudo-code.