|
1 | 1 | --- |
2 | 2 | working-groups: |
3 | | - - title: "Test classloading" |
4 | | - board-url: "https://github.com/orgs/quarkusio/projects/30" |
5 | | - short-description: | |
6 | | - The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes. |
7 | | - readme: | |
8 | | - <p>At the moment, Quarkus tests are invoked using one classloader, and then executed in a different classloader. This mostly works well, but means some use cases don't work: extensions cannot manipulate test classes in the same way that they do normal application classes. For example, anything run via a JUnit @TestTemplate test case will see the un-transformed class.</p> |
9 | | - <p>It also means we have extra user-facing complexity, such as the QuarkusTest*Callbacks](https://quarkus.io/guides/getting-started-testing#enrichment-via-quarkustestcallback):</p> |
10 | | - <blockquote> |
11 | | - <p>While it is possible to use JUnit Jupiter callback interfaces like BeforeEachCallback, you might run into classloading issues because Quarkus has to run tests in a custom classloader which JUnit is not aware of.</p> |
12 | | - </blockquote> |
13 | | - <p>A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access.</p> |
14 | | - <p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p> |
15 | | - <ul> |
16 | | - <li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</li> |
17 | | - <li>Proposal: https://github.com/quarkusio/quarkus/discussions/41867</li> |
18 | | - <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/">Zulip topic</a></li> |
19 | | - </ul> |
20 | | - status: on track |
21 | | - lts: false |
22 | | - completed: false |
23 | | - last-activity: 2025-10-23 |
24 | | - last-update-date: 2025-09-08 |
25 | | - last-update: | |
26 | | - In the last month, the WG - Test classloading achieved important milestones by successfully closing two issues related to test execution. They resolved problems with continuous testing failing in multi-module projects and addressed failures of QuarkusTests with nested classes in the IDEA IDE. However, a new issue was opened regarding the QuarkusTestProfileAwareClassOrderer, which no longer adheres to its expected contract, indicating ongoing challenges in refining the test classloading process. |
27 | | - |
28 | | - (This status update was automatically generated using AI.) |
29 | | - point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)" |
30 | | - proposal: https://github.com/quarkusio/quarkus/discussions/41867 |
31 | | - discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/ |
32 | 3 | - title: "Observability.Next" |
33 | 4 | board-url: "https://github.com/orgs/quarkusio/projects/42" |
34 | 5 | short-description: | |
@@ -98,14 +69,43 @@ working-groups: |
98 | 69 | status: on track |
99 | 70 | lts: false |
100 | 71 | completed: false |
101 | | - last-activity: 2025-10-21 |
| 72 | + last-activity: 2025-10-26 |
102 | 73 | last-update-date: 2025-09-08 |
103 | 74 | last-update: | |
104 | 75 | In the last month, the WG - Observability.Next focused on improving the observability stack within the Quarkus framework. The group successfully closed several issues, addressing duplicated OpenTelemetry metrics messages and resolving test failures related to constructor injection in @GrpcService-annotated classes. Additionally, they worked on enhancing documentation regarding the differences in semantic conventions between Micrometer and OpenTelemetry. Notably, a new documentation issue was opened to further refine the precision of this section, reflecting ongoing efforts to clarify and improve resources for users. |
105 | 76 | |
106 | 77 | (This status update was automatically generated using AI.) |
107 | 78 | point-of-contact: "@brunobat" |
108 | 79 | proposal: https://github.com/quarkusio/quarkus/discussions/44423 |
| 80 | + - title: "Test classloading" |
| 81 | + board-url: "https://github.com/orgs/quarkusio/projects/30" |
| 82 | + short-description: | |
| 83 | + The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes. |
| 84 | + readme: | |
| 85 | + <p>At the moment, Quarkus tests are invoked using one classloader, and then executed in a different classloader. This mostly works well, but means some use cases don't work: extensions cannot manipulate test classes in the same way that they do normal application classes. For example, anything run via a JUnit @TestTemplate test case will see the un-transformed class.</p> |
| 86 | + <p>It also means we have extra user-facing complexity, such as the QuarkusTest*Callbacks](https://quarkus.io/guides/getting-started-testing#enrichment-via-quarkustestcallback):</p> |
| 87 | + <blockquote> |
| 88 | + <p>While it is possible to use JUnit Jupiter callback interfaces like BeforeEachCallback, you might run into classloading issues because Quarkus has to run tests in a custom classloader which JUnit is not aware of.</p> |
| 89 | + </blockquote> |
| 90 | + <p>A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access.</p> |
| 91 | + <p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p> |
| 92 | + <ul> |
| 93 | + <li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</li> |
| 94 | + <li>Proposal: https://github.com/quarkusio/quarkus/discussions/41867</li> |
| 95 | + <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/">Zulip topic</a></li> |
| 96 | + </ul> |
| 97 | + status: on track |
| 98 | + lts: false |
| 99 | + completed: false |
| 100 | + last-activity: 2025-10-23 |
| 101 | + last-update-date: 2025-09-08 |
| 102 | + last-update: | |
| 103 | + In the last month, the WG - Test classloading achieved important milestones by successfully closing two issues related to test execution. They resolved problems with continuous testing failing in multi-module projects and addressed failures of QuarkusTests with nested classes in the IDEA IDE. However, a new issue was opened regarding the QuarkusTestProfileAwareClassOrderer, which no longer adheres to its expected contract, indicating ongoing challenges in refining the test classloading process. |
| 104 | + |
| 105 | + (This status update was automatically generated using AI.) |
| 106 | + point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)" |
| 107 | + proposal: https://github.com/quarkusio/quarkus/discussions/41867 |
| 108 | + discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/ |
109 | 109 | - title: "Spring-Style Testing" |
110 | 110 | board-url: "https://github.com/orgs/quarkusio/projects/60" |
111 | 111 | short-description: | |
|
0 commit comments