Improve Quarkus testing by preventing Vaadin servlet registration.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
Research direction
Start with the Quarkus browserless testing module and the existing user tests, then check the prerequisite vaadin/quarkus#281 behavior. Add the requested BrowserlessTestProfile and @BrowserlessQuarkusTest integration, and verify that browserless tests use the annotation without binding the HTTP server or starting the servlet container.
Written by the indexing model from the issue text.
Description
Browserless testing on Quarkus needs to mark Vaadin the test class with @QuarkusTest annotation so that all the augmentation provided by the Vaadin extension (scopes, beans, unremovables, ...) is available during test execution.
The drawback is that with @QuarkusTest, the application is started, including the servlet container and the Vaadin initialization.
With browserless testing, both are unnecessary and only slow down the execution of the tests.
After vaadin/quarkus#281 is implemented, the Quarkus browserless testing module should provide a test profile (BrowserlessTestProfile) named vaadin-browserless and a @BrowserlessQuarkusTest annotation which activates @QuarkusTest and the test profile`
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@QuarkusTest
@TestProfile(BrowserlessTestProfile.class)
public @interface BrowserlessQuarkusTest {}
The BrowserlessTestProfile class itself should also prevent the HTTP server from being bound to any port
public class VaadinFastTestProfile implements QuarkusTestProfile {
@Override
public String getConfigProfile() { return "vaadin-browserless"; }
@Override
public Map<String, String> getConfigOverrides() {
return Map.of("quarkus.http.host-enabled", "false");
}
}
User tests should then use @BrowserlessQuarkusTest instead of @QuarkusTest.
- Dominant language
- Java
- Stars
- 1
- Forks
- 3
- Avg merge
- 15h 42m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vaadin/browserless-test
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vaadin/browserless-test#291 · 1 comment ·
Maintainers usually reply within 1 day
-
(MultiSelect)ComboBoxTester add support for selectItemContaining(String)Possibly taken @totally-not-ai claimed this 21 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vaadin/browserless-test#270 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vaadin/browserless-test#266 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vaadin/browserless-test#123 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
vaadin/browserless-test#286 · 1 comment ·
Maintainers usually reply within 1 day
All issues in vaadin/browserless-test
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
strimzi/strimzi-kafka-operator#13328 · 1 comment · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
OpenLiberty/ci.maven#2137 ·
Maintainers usually reply within 1 day
-
Payer adjustment can exceed the balance left after copay and deductible, so claim payments add up to more than the chargePossibly taken @DG47 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
synthetichealth/synthea#1772 ·
Maintainers usually reply within 13 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
geonetwork/core-geonetwork#9592 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NationalSecurityAgency/ghidra#10040 ·
Maintainers usually reply within 2 days