How gsanchezm/test-oriented-microkernel-architecture works
Project Type and Purpose
• This is an open-source, extensible Test Automation Framework built in Java (with a parallel JavaScript version) using a Microkernel (plugin-based) architecture.
• The “core” module implements the microkernel—loading plugins, providing execution context, dispatching tasks/validations.
• Additional modules (“common,” “frameworks,” “plugins”) provide support libraries, platform-specific initialization handlers, and concrete test-automation plugins (Web, Mobile, API, Performance).
File Structure Analysis
• Top-level Maven reactor (pom.xml) defines sub-modules:
• common – shared utilities, config, factories, interfaces, resolvers, listeners.
• core – microkernel engine, plugin manager, exception handling, test runners.
• frameworks – platform initialization handlers/write-your-own-framework (api, web-ui, mobile-ui, performance).
• plugins – concrete plugins for various domains: selenium, rest-assured, appium, JMeter.
• ci-cd – GitHub Actions workflow for build/test.
• Each framework/plugin module has its own POM and src/main/java hierarchy.
• Common patterns: Factory, Service Locator (AutoDiscoveryPlugin), Interface-based plugins (IPlugin, ITaskFactory, IValidationFactory).
README Insights
• Emphasizes “Microkernel Architecture” with “modular test plugin” approach.
• Core execution engine loads/invokes plugins.
• CI/CD integration via Maven and Node.js scripts.
a. Main Components
• Core Microkernel
• Common Library
• Framework Modules (API, Web-UI, Mobile-UI, Performance)
• Plugin Modules (Selenium, RestAssured, Appium, JMeter)
• CI/CD Pipeline (GitHub Actions)
• External Tools/Services: Appium Server, Selenium Grid/Browser Drivers, JMeter Engine, REST endpoints
b. Relationships & Interactions
• Core depends on Common for configuration, factories, listeners.
• Core’s PluginManager dynamically loads Frameworks and Plugins at startup.
• Framework modules implement initialization handlers (e.g., IWebInitialize, IMobileInitialize) invoked by Core.
• Plugin modules implement ITask and IValidation interfaces, discovered via Common’s AutoDiscoveryPlugin.
• During test execution: Core → Framework Init → Plugin tasks/validations → External tools (Appium/JMeter/Selenium).
• CI/CD triggers Maven (and npm) builds, runs Core tests against assembled modules.
c. Architectural Patterns & Principles
• Microkernel with Plugin Manager (Inversion of Control for extensibility)
• Factory Method & Service Locator for object creation and discovery
• Interface-driven design for tasks, validations, initialization
• Modularization via Maven multi-module project
d. Key Technologies & Frameworks
• Java 17, Maven multi-module
• Interfaces: IPlugin, ITask, IValidation, IInitializeBase
• Framework-specific InitHandlers: ApiInitializerHandler, AndroidCapabilitiesLoader, PerformanceInitializerHandler, etc.
• Plugins: SeleniumPlugin, RestAssuredPlugin, AppiumPlugin, JMeterPlugin
Essential Elements to Capture
• Core/PluginManager as central orchestrator
• Common services (Configuration, AutoDiscovery)
• Framework InitHandlers for each domain
• Plugin modules as drop-in extensions
• External dependencies (Appium, Selenium Grid, JMeter)
• CI/CD flow connecting code → build → test → report