Use filestate backend for testing
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Switch testing to filestate backend both for integration tests running locally and for consistency in CI. The objective is to improve contributor experience (the local scenario). The reasoning is that we trust the cloud backend to work, the tests here are mostly helping find bugs in Java.
Affected area/feature
Contributor 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.
Research direction
Start by locating the integration tests and CI configuration in the pulumi-java repository, then identify where the current cloud backend is selected for local and CI runs. The work is done when both environments use the filestate backend and the integration tests continue to pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100