← All questions

@data:users errors with "is not a declared dataset (logins, posts)" after a rename

✖ features/auth/data-driven-login.feature:6  tags/data  @data:users is not a declared dataset (logins, posts).
✖ features/auth/pool.feature:11  tags/data  @data:users is not a declared dataset (logins, posts).

2 answers

• 15votes

  It is documentation that is checked. The tag does not load anything — your Given I load dataset "logins" ... step does that. What the tag buys you is that the dependency is visible before the run: coverage can tell you which scenarios depend on which dataset, and change analysis can tell you which scenarios to re-run when a dataset changes.

  Which is exactly what you just used it for. The step and the yaml agreed, so nothing broke; the tags disagreed, and lint told you which two files still carry a stale claim. Without the tag the rename would have been invisible.

  Valid values are the keys under data.sources:

  yamlCopy

  data:
    sources:
      logins: { type: csv, path: 'data/{env}/logins.csv', fallback: data/common/logins.csv }
      posts: { type: yaml, path: 'data/{env}/posts.yaml' }

  so @data:logins and @data:posts, and nothing else.

  RKanswered by Renata Kohl608 · 4 Dec 2024
• 7votes

  Worth pairing the tag with @data-driven while you are editing those files. @data:logins says which dataset; @data-driven says the scenario's shape is one behaviour times N rows. They answer different questions and reports use both.

  And do not put @data: on a scenario that merely happens to log in with a pool user — that relationship is @user:<role> and @pool. Overusing @data: makes the change-impact answer useless because everything depends on everything.

  PVanswered by Priya Venkateshmaintainer29,604 · 6 Dec 2024