Niitch

@dgozman For more context, here is how the wrapper is actually used: ```typescript // step-definitions/example.spec.ts import { test as base } from "@playwright/test"; import GherkinWrapper from "gherkin-wrapper"; // Add fixtures...

@dgozman It is indeed a runtime wrapper that does not generate code. The playwright wrapper is defined [here](https://github.com/Niitch/gherkin-wrapper/blob/feature/location/src/playwright/index.ts) The solution you suggest is not practicable. It would work, but I...

I knew about [vitalets/playwright-bdd](https://github.com/vitalets/playwright-bdd), but I wanted to try a non-codegen approach. I want a very playwright-native-like experience for the user. I'll search about implementing codegen and sourcemaps.

@vitalets @mattjennings The soutions you suggested are good but only work test steps. I have finally found a way to pass custom location objects for every functions of the test...

If I got it wright, what you want is to make playwright understand that the features/scenarios have been defined in your .spec.ts file, regardless that they have actually been built...

I found that the playwright `location` objects are built from stack traces by the `test.describe`/`test`/`test.step` functions by alteration of the `Error.captureStackTrace` method. I don't know yet how to alter the...

I've found a way to make it works for both the UI mode and the reporter. With this solution you will have to choose between using the ideal behaviour and...

"ideal behaviour" refers to "Playwright understood the location of the test as the feature file and line where the Example / Scenario was specified" For now, if you want to...

@NikkTod I merged and published the feature for the ui mode and the reports just now (v0.3.0). About the VSCode test explorer, I have found it would be better to...