tests: Ensure maven test sets environment
Metadata
Current evaluation
Merged changes to ensure the Maven test runs independently by properly setting its environment. Updated init.py to clear cached functions between integration tests. Approved by one reviewer, passed CI, and modified two files with 27 additions.
Suggested action: —
No scores available.
Issue body
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
I came across this while running the integration tests. As is, the maven test succeeds when running all tests in order, but fails when run without running the ant test. The change in `test_maven.py` fixes the test so it can run independently, and the change in `__init__.py` ensures that cached functions get their caches cleared after each integration test, keeping them more independent.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged changes to ensure the Maven test runs independently by properly setting its environment. Updated init.py to clear cached functions between integration tests. Approved by one reviewer, passed CI, and modified two files with 27 additions. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged changes fixing maven test isolation by ensuring the environment is set. Updated __init__.py to clear cached functions between integration tests, enabling independent execution. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #650 feature/maven-targets w/ re-based maven.py | snapcraft | merged | Merged after rebasing the maven plugin and test suite. CI failures were resolved by unmocking glob and fixing test errors. Admin verification confirmed readiness prior to integration. |