Temporal Features

This repository contains snippets for many Temporal features written in different Temporal SDK languages. This also contains a runner and language-specific harnesses to confirm feature behavior across versions.

These features serve several purposes:

• Ensure parity across SDKs by having same-feature snippets adjacent to one another
• Confirm feature behavior across SDK versions
• Confirm history across SDK versions
• Document features in different SDKs
• Easy-to-use environment for writing quick workflows in all languages/versions
• Verify feature compatibility across different server setups

Building

With latest Go installed, run:

go build -o temporal-features # or temporal-features.exe on Windows

Running

Prerequisites:

• Go 1.17+
• JDK 11+
• Node 16+
• Python 3.10+
  • Poetry: poetry install
  • setuptools: python -m pip install -U setuptools
• .NET 7+
• PHP 8.1+
  • Composer

Command:

temporal-features run --lang LANG [--version VERSION] [PATTERN...]

Note, go run . can be used in place of go build + temporal-features to save on the build step.

LANG can be go, java, ts, php, py, or cs. VERSION is per SDK and if left off, uses the latest version set for the language in this repository.

PATTERN must match either the features relative directory or the relative directory + /feature.<ext> via Go path match rules which notably does not include recursive depth matching. If PATTERN arguments are not present, the default is to run all features.

Several other options are available, some of which are described below. Run temporal-features run --help to see all options.

Preparing

By default when using run and a version, a temporary directory is created with a temporary project, the project is built, and then the features are run. To separate the steps, the prepare command can be used to prebuild the project in a directory. Then run can use the --prepared-dir to reference that directory.

The command to prepare is:

temporal-features prepare --lang LANG --version VERSION --dir DIR

The version is required and the directory is a simple string name of a not-yet-existing directory to be created directly beneath this SDK features directory. That same directory value can then be provided as --prepared-dir to run. When using a prepared directory on run, a version cannot be specified.

Building docker images

The CLI supports building docker images from prepared features.

There are 2 types of image builds supported, by SDK version or by git repository ref as shown below:

./temporal-features build-image --lang go --repo-ref master

The built image will be tagged with features:go-master

./temporal-features build-image --lang go --version v1.13.1

The built image will be tagged with features:go-1.13.1

• To tag as latest minor, pass --semver-latest minor, this will add the go-1.13 tag.
• To tag as latest major, pass --semver-latest major, this will add the go-1.13, go-1 and go tags.

External Server and Namespace

By default, a CLI Dev Server is dynamically started at runtime to handle all feature runs and a namespace is dynamically generated. To not start the embedded server, use --server to specify the address of a server to use. Similarly, to not use a dynamic namespace (that may not be registered on the external server), use --namespace.

History Checking

History files are present at features/<path/to/feature>/history/history.<lang>.<version>.json. By default, three history checks are performed:

1. Specific languages use their replayers to replay the just-executed workflow's history to confirm it works.
2. Specific languages use their replayers to replay all history files with versions <= the current version to confirm it works.
3. The primary runner scrubs the history of the just-executed workflow of all execution-dependent values. Then it compares the exact events to all similarly-scrubbed history files.

Currently there are not ways for features to opt out of specific history checks. To opt out of all history checking for a specific run, use --no-history-check.

Writing Features

Developers can write workflows and activities that represent a SDK "feature". These are organized into directories under the features/ directory.

In addition to code for the feature, there are configuration settings that can be set in .config.json. The possible settings are:

• go
  • minVersion - Minimum version in Go this feature should be run in. The feature will be skipped in older versions.

There are also files in the history/ subdirectory which contain history files used during run. See the "History Checking" and "Generating History" sections for more info.

Best Practices

• Try to only demonstrate/test one feature per feature directory.

  • Code should be kept as short and clear as possible.
  • No need to over-assert on a bunch of values, just confirm that the feature does what is expected via its output.

• A Go feature should be in feature.go.

  • For incompatible versions, different files like feature_pre1.11.0.go can be present using build tags

• A Java feature should be in feature.java.

• A TypeScript feature should be in feature.ts.

  NOTE: TypeScript features include workflow and non workflow code in the same file. Those are run in different environments so they may not share variables and the feature author should keep the workflow runtime limitations in mind when writing features.

• A Python feature should be in feature.py.

• Add a README.md to each feature directory.

  • README should have a title summarizing the feature (only first letter needs to be in title case), then a short paragraph explaining the feature and its purpose, and then optionally another paragraph explaining details of the specific code steps.
  • Other sections can also explain decisions made in language specific ways or other details about versions/approaches.
  • Feel free to add links and more text as necessary.

• Verification/regression feature directories for bugs should be under features/bugs/<lang>.

  • Ideally the checking of the result has a version condition that shows in earlier versions it should fail and in newer versions it should succeed.

• The more languages per non-bug feature, the better. Try not to create non-bug features that use specific language constructs unless that's the purpose of the feature.

• Refactor liberally to create shortcuts and better harnesses for making features easy to read and write.

  • This is not a library used by anyone, there are no backwards compatibility concerns. If one feature uses something that has value to another, extract and put in helper/harness and have both use it.

• History should be generated for each feature on the earliest version the feature is expected to work at without history changes.

Generating History

To generate history, run the same test (see the "Running" section) for the version to generate at, but use the --generate-history option. When generating history, only one test can be specified and the version of the SDK must be specified. Any existing history for that feature, language, and version will be overwritten.

History generation should only be needed when first developing a feature or when a version intentionally introduces an incompatibility. Otherwise, history files should remain checked in and not regenerated.

Usage within CI

The repo defines GitHub workflows which are designed to allow running the SDK features suites against changes to an SDK, or against changes to server. The former is accomplished by syncing the SDK repo and using it as a path-version when running the suites. The latter is accomplished by building the changes to server into a docker image, and using that docker image for the server when running the suites.

Publishing docker images of the features runner/suites is also supported. It may be run manually, but is also triggered by default on each push to main.

The dynamic configuration file located at dockerfiles/dynamicconfig/docker.yaml defines the dynamic configuration settings needed for features to run, and should be used as part of or all of the dynamic config settings for any external server not using the basic docker-compose setup.

TODO

• Add support for replaying testing of all versions inside each SDKs harness as part of the run
• Add many more feature workflows
• Document how to use this framework to easily write and test features even when not committing
• Log swallowing and concurrent execution
• Investigate support for changing runtime versions (i.e. Go, Java, and Node versions)
• Investigate support for changing server versions
• CI support
  • Support using a commit hash and alternative git location for an SDK to run against