Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
sdods lint -p demo-shopUndefined step: Given I am on the checkout pageThe class has it:
@Given('I am on the checkout page')
async open() {
await this.goto('checkout');
}Spelling matches character for character, I diffed it. The file is pages/CheckoutPage.ts. What else is there to check?
Accepted answer
Two causes, and the file location rules out the first one for you.
pages/**/*.ts or steps/**/*.ts. Yours is, so skip it.@Fixture<typeof test>('checkoutPage') names a fixture in steps/fixtures.ts, and if that name is not in the extend call — or is spelled checkoutPageObject, which is what bit me — the decorated methods have nothing to attach to and generation reports them as missing.export const test = base.extend<{ checkoutPage: CheckoutPage }>({
checkoutPage: async ({ pages }, use) => use(pages.get(CheckoutPage)),
});Separately, and I would fix this before the other thing: that step probably should not exist. The shared library already ships I navigate to the "checkout" page, which resolves the route name from sdods.project.yaml and does the same navigation. Check before you write:
sdods steps list -p demo-shop --grep checkoutKeep the page object for the parts of checkout that are actually yours.
For context on where the message comes from: sdods lint runs generation with missing steps set to fail, then parses the block it prints. So the finding is reported against the feature file and line that used the step, not against the page object — which is why the location in the output looks unhelpful when the real problem is in steps/fixtures.ts.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.