Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to setup dev env / run tests? #96

Open
nrser opened this issue Nov 26, 2018 · 0 comments
Open

How to setup dev env / run tests? #96

nrser opened this issue Nov 26, 2018 · 0 comments

Comments

@nrser
Copy link

nrser commented Nov 26, 2018

I'm trying to try out my fix to #94, but I'm not sure how to get a local development environment setup and run tests (if there are any?):

  1. I didn't see any instructions in README.md or test tasks Rakefile.
  2. Gemfile.lock is committed, so I'm assuming I should be developing and testing with those exact versions? However, it lists the yard-cucumber gem itself as 3.1.0 when the source is at 4.0, which prevents a --frozen install. I assume this an oversight or missed commit?
  3. After manually changing the yard-cucumber version in Gemfile.lock I can install the gems with bundler, but I'm not sure how to run the Cucumber tests (I'm new to Cucumber), or if the features in example/ are tests of the gem or just general examples...
    1. bundle exec cucumber fails not finding a features/ directory.
    2. bundle exec cucumber example fails with a parser error on example/empty.feature.
  4. There is a .rspec file in the project root but rspec is not included in yard-cucumber.gemspec or Gemfile, and I don't see a spec/ directory specs anywhere else.
  5. bundle exec rake gendoc has errors for README.md files in example/.
nrser added a commit to nrser/yard-nrser-cucumber that referenced this issue Nov 26, 2018
Attempts to fix "uninitialized constant <Module:...>::TreeContext"
failure when generating the class list nav running `yard server`.

See burtlo#94 for details.

If there are tests, I haven't figured out how to run them (see
burtlo#96 for details).
@nrser nrser mentioned this issue Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant