Hi Jeremy, I updated my Ruby version to 2.1.2p95, and I ran the tests from the integration_tests/agility_bootstrap folder:
vagrant@precise-base:/vagrant/hobo/integration_tests/agility_bootstrap$ rake test:integration [deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message. Run options: --seed 2790 # Running tests: ....... Finished tests in 97.898039s, 0.0715 tests/s, 1.3483 assertions/s. 7 tests, 132 assertions, 0 failures, 0 errors, 0 skips Maybe you are running the tests from the older "agility" app, which uses the clean theme? Those tests will probably need some cleanup to pass. Warm regards, Ignacio El 21/07/14 14:26, JezC escribió: > Hiya - I'm about to commit a branch to my JezC/hobo fork (test-spike), > that updates and extends the documentation about the Unit Testing - i.e. > I wrote up the bits that I fell foul of ;) > > As of today, using the master hobo branch (2.1.1 and a a bit), rails > 4.0.8, ruby 2.1.2, the first integration test yields: > > 7 tests, 10 assertions, 1 failures, 5 errors, 0 skips > > The second (AJAX) test yields: > > 1 tests, 17 assertions, 0 failures, 1 errors, 0 skips > > Does that match what you're seeing? > > If not, I probably have something else to sort out, before I take the > tests seriously ;) > > Cheers, JeremyC. > > > On Sunday, 20 July 2014 17:24:04 UTC+1, Ignacio Huerta wrote: > > Hi Jeremy, > > I'm afraid that Unit tests have been neglected for the last couple of > releases. I believe most of them will work, but a lot of gem > updates/syntax changes might make it difficult to set them up. > > It would be really great if you could get the unit tests to run and > update the documentation about that. As a first step, I just made a > commit updating the Rails versions in the Gemfiles of each of the gems: > > https://github.com/Hobo/hobo/commit/42c39be3ad940931a1ab1dd4906da755db2b7852 > > <https://github.com/Hobo/hobo/commit/42c39be3ad940931a1ab1dd4906da755db2b7852> > > > This should get you one step further. Then I'm getting errors with some > of the new Rails4 code, but maybe you can take a look at it. > > Warm regards, > Ignacio > > PS: If you are interested, what we've been using successfully is the > integration_tests/agility_bootstrap folder. This contains an > application > with a lot of Capybara tests. They help a lot to make sure nothing > major > is broken with the Hobo stack. > > El 20/07/14 15:36, JezC escribió: > > I've made a fork of the Github repo, to do some tinkering. > > > > I wanted to run the various tests on my machines before I started > > changing anything in my fork. > > > > I'm following the description in hobo/README.md for the Unit > Tests. This > > document is probably outdated - there's a reference to the > > CHANGES-1.4.txt, for example. That may be why I'm having > difficulties. > > > > I created a new clean gemset ('hobo-test'), then did the set up > for the > > test: > > > > export HOBODEV=`pwd` > > > > to get the Current Working Directory into a parameter for the script > > that follows. > > > > for f in dryml hobo_support hobo_fields hobo ; do cd $f ; bundle > > install ; cd .. ; done > > > > When I execute the shell commands, I get several warnings and one > failure: > > > > Bundler could not find compatible versions for gem "actionpack": > > > > > > > > In Gemfile: > > > > > > > > dryml (>= 0) ruby depends on > > > > > > > > actionpack (~> 4.0.2) ruby > > > > > > > > > > rails (= 3.2.12) ruby depends on > > > > > > > > actionmailer (= 3.2.12) ruby depends on > > > > actionpack (3.2.12) > > > > Looking at my gem list, I see that Rails 4.0.8 has been picked up. > There > > is no railties or other Rails component at 3.2.x. actionmailer is > at 4.0.8. > > > > There must be something else about the test environment that isn't > > documented, I think. > > > > I also see that there are two versions of rake that are installed. > This > > implies that one of those subdirectories is requiring something > > different from the others, and applying different constraints. That's > > perfectly plausible - I understand that some of the components can be > > used separately from Hobo. > > > > What am I missing in the setup for doing Unit Tests? > > > > Cheers, JeremyC > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Hobo Users" group. > > To unsubscribe from this group and stop receiving emails from it, > send > > an email to [email protected] <javascript:> > > <mailto:[email protected] <javascript:>>. > > To post to this group, send email to [email protected] > <javascript:> > > <mailto:[email protected] <javascript:>>. > > Visit this group at http://groups.google.com/group/hobousers > <http://groups.google.com/group/hobousers>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google > Groups "Hobo Users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/hobousers. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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 http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
