On Friday, January 4, 2019 at 7:39:46 AM UTC-8, [email protected] wrote: > > Excellent, thank you. I wasn't sure what workflow / setup steps were > needed. >
In general, "gem install --development sequel" should be all you need. You shouldn't need to install bundler or use bundle exec, just a bare rake in the sequel repository should be sufficient. > In addition to the below, on a clean environment I also had to add the > 'rdoc' gem, but then it worked beautifully. > rdoc is included with ruby, so it shouldn't need to be installed separately. > Are there any other articles or info about how the testing is set up (not > unit testing specifically, but rake, using with bundler, what folder > structure is needed, what files are read, etc)? > There is http://sequel.jeremyevans.net/rdoc/files/doc/testing_rdoc.html#label-Testing+Sequel+Itself, but that's about it. It lists some additional rake tasks you can use for testing parts that aren't part of the default rake task (such as the adapter tests). No special folder structure is needed, all tests should work with Sequel's repository without additional changes. Which files are read depends on which rake tasks are executed. Pretty much all test files can be run individually using ruby: ruby spec/core/database_spec.rb To run specific tests, you can run them by name: ruby spec/core/database_spec.rb -n '/should be chainable/' or by line number with the m gem: m spec/core/database_spec.rb:1000 Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
