How zebrunner/carina works
Project Type and Purpose
• This is an open-source Java-based test automation framework (Carina) that provides a unified API for Web, Mobile (iOS/Android), Windows, REST services, databases, and reporting.
• It consists of a core library (carina-core) plus optional modules (carina-api, carina-azure, carina-aws-s3, etc.) and an archetype project to generate new test projects.
Main Components
a. Carina Core Modules (src/main/java/com/zebrunner/carina)
• Core engine: AbstractTest, IAbstractTest
• Configuration: ReportConfiguration, TestConfiguration
• Session creation & WebDriver wrapper (carina-webdriver)
• Filters & rules (v1, v2 filter subsystems)
• Listeners (TestNG listeners chain, CarinaListener)
• Reporting connectors (Email, QTest, TestRail)
• Utilities: DateUtils, RetryAnalyzer, ParameterGenerator, ArtifactUtils, ConnectionFactory
b. Archetype Project (archetype/)
• Maven archetype that scaffolds a Carina-powered test project, with sample packages for API, DB, GUI, SOAP, WebSocket, mobile.
c. Resources & Configuration
• src/main/resources: localization (L10N), capabilities.properties, config.properties, mybatis.config.xml, log4j2.xml
• Archetype resources: _config.properties, database/email/testdata properties, test data sources (CSV, XLSX), Freemarker templates for API.
d. Optional Modules
• carina-api (RestAssured + Freemarker for REST)
• carina-aws-s3, carina-azure, carina-appcenter, carina-dataprovider, etc.
e. Documentation & Site
• docs/: mkdocs documentation, getting started guides, advanced topics, architecture overviews.
Relationships & Data Flows
• User test code (extends AbstractTest) → Carina Core
→ SessionFactory (WebDriver/Appium) ↔ Selenium/Appium servers or cloud providers (BrowserStack)
→ Execution on target (Web/Mobile/Windows) → Listeners gather results
→ Report generators push to Email/QTest/TestRail/Zebrunner
• DB layer uses MyBatis mappers + models to read/write data.
• API tests use Freemarker templates + RestAssured.
• Configuration & capabilities read from properties files.
• Archetype generates project skeleton that plugs into Carina Core and optional modules.
Architectural Patterns & Principles
• Layered architecture: Test layer → Core engine → Driver/session layer → External tools/services.
• Plugin/extensibility via interfaces (carina-commons) and ServiceLoader (META-INF/services/org.testng.ITestNGListener).
• Separation of concerns: filters, listeners, reporters, utilities each in separate packages.
• Maven modularity: “carina-core” artifact plus optional JARs.