Known limitations

Sequential runner invocations

Currently, tests using act can't be reliably invoked in parallel. This is caused by act generating stable container names based on the workflow's name property. If your tests run in-parallel and reuse the same workflow file, then the generated container names will collide, resuling in test failures. If you still want to run your tests concurrently, ensure that the workflows have unique names. See nektos/act#1287 for mode details.

Supported act options

act provides a large number of options to configure workflow execution. This library aims to abstract away the configuration effort and enforce best practices. Therefore, the initial release of the library has a built-in support for a small set of options deemed essential to design meaningful test scenarios for GitHub workflows.

Additional unsupported arguments can be passed using the additionalArgs property of a ActRunner object. Despite having this option, feel free to submit a feature request for a new option describing how the library and its users will benfit from having a native support for this property.