temporalio / temporalio/features
Nexus operation testing environment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Nexus operation authors, like activity authors, need an environment to test their Nexus operations. It's probably just the ability to mock and trigger certain situations without server involvement, much like activity test environments. This environment should probably be built in the non-Temporal Nexus SDKs then the Temporal SDKs can add features.
Per-SDK Tickets
- Go - TODO
- Nexus Go - TODO
- Java - TODO
- Nexus Java - TODO
- Core - N/A
- TypeScript - TODO
- Nexus TypeScript - TODO
- Python - TODO
- Nexus Python - TODO
- .NET - TODO
- Nexus .NET - TODO
- Ruby - TODO
- Nexus Ruby - TODO
- PHP - TODO
- Nexus PHP - TODO
- Temporal CLI - N/A
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 files, tests, or entry points are named. Start by comparing the requested Nexus operation environment with existing activity test environments and scope the non-Temporal SDK work; done means the relevant SDK tickets have defined and implemented test environments for mocking and triggering operation situations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, ruby, typescript
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100