Skip to content

Document how to check which bundles a test run actually uses #2407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vogella wants to merge 1 commit into from
Closed

Document how to check which bundles a test run actually uses #2407

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,17 @@ mvn verify -pl :org.eclipse.pde.ui.tests -Pbuild-individual-bundles -Dtest=Depen
mvn verify -pl :org.eclipse.pde.core,:org.eclipse.pde.ui.tests -Pbuild-individual-bundles
```

Every bundle not listed in `-pl` is taken from the target platform as a released bundle, so a changed bundle that the test bundle only reaches indirectly is not covered.
`-am` (`--also-make`) builds the whole upstream closure of the test bundle from source instead:
```bash
mvn verify -pl :org.eclipse.pde.ui.tests -am -Pbuild-individual-bundles -Dtest=DependencyLoopFinderTest
```

**Confirm the test runtime really uses your build.**
A test that passes or fails against a released bundle says nothing about the change.
After a run, `ui/org.eclipse.pde.ui.tests/target/work/configuration/config.ini` lists the bundles the harness installed: an entry under the local `target/` directory is your build, one under `~/.m2/repository/p2/` is the released bundle.
Only the test bundle itself is additionally mapped to its class folders, through `target/work/dev.properties`.

**Headless (Wayland-safe):** pin the GTK backend to X11 so the UI test harness renders on Xvfb instead of the real compositor:
```bash
GDK_BACKEND=x11 xvfb-run -a mvn verify -pl :org.eclipse.pde.ui.tests -Pbuild-individual-bundles -Dtest=DependencyLoopFinderTest
Expand Down
Loading