Skip to content

Commit 2078185

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 8f7c20b commit 2078185

File tree

1 file changed

+29
-26
lines changed

1 file changed

+29
-26
lines changed

‎_data/wg.yaml‎

Lines changed: 29 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,30 @@
11
---
22
working-groups:
3+
- title: "Test classloading"
4+
board-url: "https://github.com/orgs/quarkusio/projects/30"
5+
short-description: 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.
6+
readme: |
7+
<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>
8+
<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>
9+
<blockquote>
10+
<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>
11+
</blockquote>
12+
<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>
13+
<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>
14+
<ul>
15+
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</li>
16+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/41867</li>
17+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/">Zulip topic</a></li>
18+
</ul>
19+
status: on track
20+
completed: false
21+
last-activity: 2025-03-13
22+
last-update-date: 2025-03-03
23+
last-update: |
24+
Code cleanup underway to remove TODOs and the most egregious hacks. CI is (mostly, sometimes) green: https://github.com/quarkusio/quarkus/actions/runs/13628335866/job/38090976898
25+
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
26+
proposal: https://github.com/quarkusio/quarkus/discussions/41867
27+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/
328
- title: "Chappie"
429
board-url: "https://github.com/orgs/quarkiverse/projects/8"
530
short-description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
@@ -19,9 +44,12 @@ working-groups:
1944
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/45377</li>
2045
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev">Zulip topic</a></li>
2146
</ul>
22-
status: inactive
47+
status: on track
2348
completed: false
2449
last-activity: 2025-03-13
50+
last-update-date: 2025-03-13
51+
last-update: |
52+
Work started.
2553
point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)"
2654
proposal: https://github.com/quarkusio/quarkus/discussions/45377
2755
discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev
@@ -44,31 +72,6 @@ working-groups:
4472
deliverable: TBD
4573
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
4674
proposal: https://github.com/quarkusio/quarkus/discussions/46627
47-
- title: "Test classloading"
48-
board-url: "https://github.com/orgs/quarkusio/projects/30"
49-
short-description: 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.
50-
readme: |
51-
<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>
52-
<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>
53-
<blockquote>
54-
<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>
55-
</blockquote>
56-
<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>
57-
<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>
58-
<ul>
59-
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</li>
60-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/41867</li>
61-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/">Zulip topic</a></li>
62-
</ul>
63-
status: on track
64-
completed: false
65-
last-activity: 2025-03-12
66-
last-update-date: 2025-03-03
67-
last-update: |
68-
Code cleanup underway to remove TODOs and the most egregious hacks. CI is (mostly, sometimes) green: https://github.com/quarkusio/quarkus/actions/runs/13628335866/job/38090976898
69-
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
70-
proposal: https://github.com/quarkusio/quarkus/discussions/41867
71-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/
7275
- title: "Quarkus 3.15 LTS"
7376
board-url: "https://github.com/orgs/quarkusio/projects/28"
7477
short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)

0 commit comments

Comments
 (0)