We're only looking at the top-level features directory by default, we should recurse through child directories

[0xste]

We should recurse through the default ./features directory by default, we should make the code search subdirectories for .feature files

.paniconexit0 -test.run ^\QTestCheckout\E$
=== RUN   TestCheckout
    runner_test.go:47: no tests found in paths: []
--- FAIL: TestCheckout (0.00s)

[aaronc]

This uses filepath.Glob currently. We could try features/**/*.feature but I'm not sure Glob supports **. We could add some different logic in Run if it doesn't.

[0xste]

Looks like we'd need to change the logic given it seems it's not natively supported in path/filepath golang/go#11862

Will put together an MR making use of likely https://github.com/bmatcuk/doublestar package referenced in the thread

[0xste]

#26

Would be good to distinguish between the directories in the repo for:

• features
• _examples

I think there's a few clear categories here:

• Library tests
  • Ensure the library works as expected
• User-facing usage examples
  • Some good examples of library usage

I've somewhat blurred the lines a little here,

I propose we rename the directory for "Library tests" or move it under the "internal" package, and ensure examples are user-focused usage examples as part of this MR 🙏