Framework-agnostic core shared by all DoQA JVM adapters (JUnit 5, TestNG, ...): the Doqa runtime facade, @Doqa* attribution annotations, the AspectJ @Step aspect, the step tree and per-test runtime context, attribution (explicit id / id-in-title / Allure bridge / signature hash), {param} placeholders, result projection and the reporting session (API batch/streaming or Allure-files sink) on top of doqa-client.

JUnit 5 adapter for DoQA: reports test results with steps, fixtures, parameters, attachments and links either directly to the DoQA API or as Allure-compatible result files, driven by annotations (@DoqaId, @DoqaTitle, ...), the Doqa ...