Gherkin | Gherkin parser , written in PHP for Behat project | Functional Testing library

Gherkin syntax doesn't have support of meta-data. You can use BDD2 syntax which is superset of Gherkin. In BDD2 you can provide scenario metadata on top of scenario:

Feature File

Looks like version compatibility issue. Use latest version of qaf 3.1.0-RC2 with testng 7.4.0.

Updating version will fix above error, still you will see issue related to step. The reason is following steps:

You should use the name of the column Gherkin inside the function VALUES() and not the named parameter ?Gherkin:

Cypress commands yield their results, and do not return them. I would suggest that you re-write your test to either not require the table element to be returned, or use an alias.

Unfortunately, the Gherkin language is not currently supported by Google Cloud Functions, as you can see here, because they are executed in language-specific runtimes:

Cloud Functions can be written in Node.js, Python, Go, Java, .NET, Ruby, and PHP programming languages, and are executed in language-specific runtimes.

Even though you can add Python dependencies, the language must be Python; as you are trying to deploy Gherkin code, I would suggest trying to use the library instead of the CLI, in which case you can have more chances to succeed, as the language used is still Python. That way, you don’t have to use .feature files. You can see how to add the dependency in the link mentioned above.

Using the library is the preferred way to use Gherkin, since it produces easily consumable AST and Pickle objects in-process without having to fork a CLI process or parse JSON.

The library itself provides a stream API, which is what the CLI is based on. This is the recommended way to use the library, as it provides a high level API that is easy to use.

If in any case you find trouble using the library, you can still change to Google Cloud Run, as it has a similar approach of serverless architecture with the freedom of using any language, library or binary.

Any language, any library, any binary.

Use the programming language of your choice, any language or operating system libraries, or even bring your own binaries.

One possibility is to add a context attribute in before_all to keep track of whether the step in question has executed before or not. This will still show the step in the logs but subsequent attempts will be no-ops.

To anyone with this problem, already bypassed the problem with:

It looks like you have you have RegExp language support injected in the string literal, because it appears to be a RegExp error. Invoke Alt+Enter on a literal with the error and the action Check RegExp should be in the list. In this case you should invoke Uninject Language or Reference in the same list to fix the problem.

Try using meta-data filter. For example: