When we converted cucumber-js from JavaScript to TypeScript, we used the any type quite liberally to hasten the process.

We have a long-term goal to replace all instances of any with the suitable type.

This would make a great first-timer contribution to potter around in the code and get to know it. As always, you can find the commiters in the https://cucumber.io/community#slack if you ne

Environment variables are documented here: https://devcenter.bitrise.io/builds/available-environment-variables/

To get started, add an entry to https://github.com/cucumber/cucumber/blob/master/create-meta/ciDict.json and run the tests...

Currently the InjectorSource is created by looking up the guice.injector-source properties from the cucumber.properties file.

Unfortunately this system is separated from the usual properties parsing. This means that for example when using JUnit5 which uses `junit-platform.propert

Please answer these questions before submitting a bug report.

What version of godog are you using?

> godog -version
Godog version is: v0.11.0

What version of Go are you using?

> go version
go version go1.15.6 darwin/amd64

What did you do?

• Add a step to a feature file including a DocString which has no registered step definition.
• Execute: `godog ru

Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a

Описание ошибки

Failed
Отчет.АнализЗамеровПроизводительности.ФормаНастроек - <АдминистраторМСК>
Overview History Retries
{ОбщаяФорма.ФормаНастроекОтчета.Форма(34)}: Не передан служебный параметр "НастройкиОтчета".
	ВызватьИсключение НСтр("ru = 'Не передан служебный параметр ""НастройкиОтчета"".'");
Categories: Product defects
Severity: normal
Duration:  205ms
Description
ТестДол

Sharing feature files amongst several projects means that only some of the features need to be tested in some codebases. One mechanism for managing this is tags, so one can filter out those scenarios that are to be ignored.

We should be able to specify the default tags in the builder so they don't need to be hacked in somewhere else.

There are many cases where people might want SSH to run on unusual ports:

• in https://bugzilla.suse.com/show_bug.cgi?id=1175849, I describe a method to traverse NAT (issue #11839) using a SSH jump host listening on port 2222;
• sometimes it's needed to traverse firewalls on ports different than port 22;
• some admins do experiments on port 23 before switching to regular port 22;
• whatever