What will my generated test class be called, and which package does it land in?

[dmytro-stasyuk]

I can't work out what decides the generated class's name — the class I put @Gherkin2JUnit on, or the spec file. And what decides which package it ends up in?

[dmytro-stasyuk]

Both come from the spec file itself — not from the class you put the annotation on.

The name is the spec file's own name, without its extension, plus a suffix:

specs/ShoppingCart.specb   →   ShoppingCartScenarios

The suffix is Scenarios by default. In concrete mode it's Test instead. Both are
configurable.

This is the same however you point SpecBinder at your specs — one exact path, or letting it find
several for you. A class named ShoppingCartFeature pointing at ShoppingCart.specb still
produces ShoppingCartScenarios, not ShoppingCartFeatureScenarios.

The package is the folder the spec file sits in, read as a package path:

Spec file	Generated class
specs/ShoppingCart.specb	specs.ShoppingCartScenarios
specs/user/Login.specb	specs.user.LoginScenarios
specs/cart/AddToCart.specb	specs.cart.AddToCartScenarios

So a class sitting in com.acme.cart that points at specs/Cart.specb produces
specs.CartScenarios. If you want the generated classes in a particular package, move the spec
files into a matching folder.

On disk the generated file appears under target/generated-test-sources/test-annotations/
with Maven, or build/generated/sources/annotationProcessor/ with Gradle, in folders matching
that package.

One thing worth knowing up front: because the name follows the file, renaming a spec file
renames the generated class too.