[test] Increase code coverage.

[jmolivas]

Test for commands.

• CacheRebuildCommand
• ChainCommand
• ConfigDebugCommand
• ConfigEditCommand
• ConfigExportCommand
• ConfigExportContentTypeCommand
• ConfigExportSingleCommand
• ConfigImportCommand
• ConfigImportSingleCommand
• ConfigOverrideCommand
• ContainerDebugCommand
• CronDebugCommand
• CronExecuteCommand
• DrushCommand
• GeneratorAuthenticationProviderCommand
• GeneratorCommandCommand
• GeneratorConfigFormBaseCommand
• GeneratorContentTypeCommand
• GeneratorControllerCommand
• GeneratorEntityCommand
• GeneratorEntityConfigCommand
• GeneratorEntityContentCommand
• GeneratorFormCommand
• GeneratorModuleCommand
• GeneratorPermissionCommand
• GeneratorPluginBlockCommand
• GeneratorPluginConditionCommand
• GeneratorPluginFieldCommand
• GeneratorPluginFieldFormatterCommand
• GeneratorPluginFieldTypeCommand
• GeneratorPluginFieldWidgetCommand
• GeneratorPluginImageEffectCommand
• GeneratorPluginImageFormatterCommand
• GeneratorPluginRestResourceCommand
• GeneratorPluginRulesActionCommand
• GeneratorPluginTypeAnnotationCommand
• GeneratorPluginTypeYamlCommand
• GeneratorServiceCommand
• GeneratorThemeCommand
• InitCommand
• MigrateDebugCommand
• MigrateExecuteCommand
• MigrateLoadCommand
• ModuleDebugCommand
• ModuleDownloadCommand
• ModuleInstallCommand
• ModuleUninstallCommand
• RestDebugCommand
• RestDisableCommand
• RestEnableCommand
• RouterDebugCommand
• RouterRebuildCommand
• SelfUpdateCommand
• SiteMaintenanceCommand
• SiteModeCommand
• SiteNewCommand
• SiteStatusCommand
• TestDebugCommand
• TestRunCommand
• UpdateDebugCommand
• UpdateExecuteCommand
• UserLoginCleanAttemptsCommand
• UserPasswordHashCommand
• UserPasswordResetCommand
• ViewsDebugCommand
• ViewsDisableCommand
• ViewsEnableCommand
• YamlMergeCommand
• YamlUpdateKeyCommand
• YamlUpdateValueCommand

Tests for helpers.

Tests for the rest of the project classes.

[heddn]

Will this cover creating instances of code for each of the console's menu options? For example, the field generated code right now has some errors in it that a php lint would pick up. Then after that, it also has some issues where if the annotations are incorrect, then you can't use the widget or formatter from the UI. The later isn't something I think would be easy to pick up with a unit test. But the first would be a good step in the right direction.

[jmolivas]

@heddn we need to implement test for source code and also for the generated code.

I will write a proposal about how to handle it, we can probably use => https://github.com/jmolivas/phpqa for both cases.

Some of the project maintainers are already using this tool to analyze and fix the project code base.

[novia713]

i would like to help here,
can anybody give a concise guideline on how to do this?
specially how to put in practise these tests once written?