temporalio / temporalio/features
[Feature Request] Test workflow changes are deterministic/nondeterministic
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Add feature test that the same changes to a workflow written in different language are considered deterministic/non deterministic. Ideally if a change is non deterministic in one SDK it should be non deterministic in all languages
Contributor guide
No contributing guide indexed for this repository
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
No file or test entry point is named. Start by locating the existing feature tests for workflow determinism and the SDK-specific checks, then compare how equivalent workflow changes are classified across languages. Done means a test demonstrates consistent deterministic or non-deterministic results across the relevant SDKs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100