Context:
In the initial design of the Fern Ginkgo client, we assumed the test suite configuration would reside at the root level of a project. However, Ginkgo's recommended practice is to have a test suite for each package.
Following this approach, now fern-ginkgo client's Report method is used to report from each test suite individually for a single test run. As a result, we end up with multiple test run entries, each corresponding to a different test suite.
This issue aims to aggregate all the reports from individual test suites and treat them collectively as a single test run.
Context: In the initial design of the Fern Ginkgo client, we assumed the test suite configuration would reside at the root level of a project. However, Ginkgo's recommended practice is to have a test suite for each package.
Following this approach, now fern-ginkgo client's Report method is used to report from each test suite individually for a single test run. As a result, we end up with multiple test run entries, each corresponding to a different test suite.
This issue aims to aggregate all the reports from individual test suites and treat them collectively as a single test run.