← All questions

Warning: "Feature is not under a declared module directory" — but the file runs fine

⚠ features/smoke-checks.feature:1  module/unassigned  Feature is not under a declared module directory (features/auth, features/inventory, features/cart, features/api, features/hybrid).
1 feature file(s), 0 error(s), 1 warning(s)

2 answers

• 20votes✓

  Accepted answer

  Move the file, in almost every case. Modules are the unit that carries ownership and expectations — owner, jira component, the routes and endpoints it covers, the tags every scenario in it should have, and the testing types it is allowed to declare. A feature outside all of them has none of that, and it will not show up under a module in coverage.

  The list in the message is built from your own modules block, so it is telling you the whole set of valid homes:

  yamlCopy

  modules:
    - name: cart
      title: Cart
      path: cart
      layers: [ui]
      testingTypes: [functional, regression]
      tags: ['@cart']
      routes: [cart, checkout]

  path defaults to name, which is why features/cart/ works with no path line at all. If your file really is a cross-cutting set of checks that belongs to nothing, declare a module for it — that is cheaper than living with the warning and eventually ignoring warnings generally.

  RNanswered by Reeta Nandalmaintainer41,280 · 14 Mar 2022
• 6votes

  Worth adding that the rule only fires when you have modules at all. A project with an empty modules list never gets this warning, so if you are early and still shuffling directories you can leave modules out until the shape settles.

  MKanswered by Marijn Kuiper18,840 · 16 Mar 2022