Skip to content
Commits on Dec 1, 2015
  1. @latortuga
Commits on Nov 30, 2015
  1. @latortuga
  2. @latortuga

    Merge pull request #530 from kgrz/use-bundler-dsl-to-make-errors-expl…

    latortuga committed
    …icit
    
    Use bundler/setup instead of custom loading code
  3. @latortuga
  4. @latortuga

    Rescue both LoadError and NameError in Gemfile load

    latortuga committed
    On Ruby 2.2.x, this throws a NameError exception because Zeus hasn't been
    loaded yet.
  5. @latortuga

    Merge pull request #532 from kgrz/simplify-load-tracking-checking-logic

    latortuga committed
    Simplify load tracking logic
  6. @latortuga
Commits on Oct 6, 2015
  1. @kgrz

    Remove extra space

    kgrz committed
  2. @kgrz
  3. @kgrz
  4. @kgrz

    Simplify load tracking logic

    kgrz committed
    1. Check the file if it exists in the LOAD_PATH before checking if it
    exists locally. If it's in the load path, use that path. If not, check
    for it's existence locally.
    
    2. We expand the file path first, which simplifies the checking of the
    file's existence in the LOAD_PATH or on the file system.
Commits on Sep 27, 2015
  1. @latortuga

    Merge pull request #526 from stripe/vagrant-code-reloading

    latortuga committed
    Vagrant code reloading
Commits on Sep 1, 2015
  1. @doy
  2. @doy

    add a listener which listens for changed files over the network

    doy committed
    presumably from a process on the other end that is actually doing the
    watching
Commits on Jun 30, 2015
  1. @kgrz

    User bundler/setup instead of custom loading code

    kgrz committed
    Adding "require 'bundler/setup'" to a file will add the bundled gems to
    the load path. This is a much safer way to load gems instead of using
    `gem <gemname>, <version>` where version is parsed from the Gemfile.
    
    Loading 'bundler/setup.rb' does the following things:
    
    1. Cleans load path, whose one function is to removing system gems from the
       load path.
    2. Loads the gem specs from Gemfile.lock
    3. Sets up the following path variables:
       BUNDLE_BIN_PATH
       BUNDLE_GEMFILE: location of the Gemfile
       PATH: Appends the location of `bundle` executable for the current
             Ruby version to the PATH.
       RUBYOPT
       RUBYLIB
    3. Activate the loaded Gem file specs. This is where the command would
       throw an exception if there's a conflict in the case where a
       different version of a particular gem in the Gemfile.lock has already
       been loaded.
    
    This makes the process more transparent. If there are any conflicts, an
    exception would be raised and this can be caught and the resulting
    backtrace can be handled properly.
Commits on May 19, 2015
  1. @latortuga

    Merge pull request #513 from leods92/patch-1

    latortuga committed
    Injected Rails Console helpers when Pry is used.
  2. @latortuga

    Expand tests for test runner integration and engage Rspec autorun

    latortuga committed
    This uses the same strategy as Minitest, namely replacing ARGV and running
    via RSpec's native autorun hook.
Commits on Apr 22, 2015
  1. @latortuga
Commits on Apr 14, 2015
  1. @latortuga

    Remove hacks around Minitest internals, make use of Minitest.autorun

    latortuga committed
    Instead of trying to hack around Minitest internals, we'll simply hook into
    the way that they internally call Minitest.run(ARGV) by replacing ARGV with
    our desired test arguments. This is arguably a hack because we're mangling
    ARGV but Minitest has executed with ARGV explicitly passed in for at least
    two major releases so we'll go with it for now.
Commits on Apr 9, 2015
  1. @leods92
Commits on Jan 13, 2015
  1. @e2

    add missing rake dep during gem build

    e2 committed
  2. @e2

    reorganize deps for Travis + MRI 1.9

    e2 committed
  3. @e2
Commits on Jan 7, 2015
  1. @latortuga

    Merge pull request #498 from sshao/refactor_specs

    latortuga committed
    Refactor specs
Commits on Dec 23, 2014
  1. @sshao

    refactored structure of m_spec.rb

    sshao committed
  2. @sshao
  3. @sshao

    stubbed ENV['...']= instead of actually setting it

    sshao committed
    this way if the expectation fails, it won't pollute other specs.
  4. @sshao

    fixed specs to use rspec 3 syntax

    sshao committed
  5. @sshao
  6. @sshao

    changed "zeus test" (w/o args) to use M for non-rspec tests

    sshao committed
    as opposed to shelling out to `rake test`, which was slower.
    assumes that tests are located in the "test" directory
Commits on Dec 22, 2014
  1. @sshao

    fixed "zeus test" (w/o args) to run rspec suite

    sshao committed
    if there are two test frameworks in the rails project and one of
    them is rspec, then "zeus test/rspec/testrb" without arguments
    runs the rspec suite by default
  2. @sshao

    fixed invocation of rake test

    sshao committed
    use Rake::Application #init, #load_rakefile, #invoke_task
    to run `rake test`. taken from the implementation of
    Rake::Application#run
Commits on Nov 10, 2014
  1. @latortuga

    Support rspec 3.0+ out of the box

    latortuga committed
    Rspec 3.0 introduces separate _helper files for full tests and tests that
    don't require the full rails app to be loaded. Because of this and because
    the point of zeus is to pre-load your app, default to loading the full
    rails_helper for zeus. You can override this behavior with the env var
    RAILS_TEST_HELPER.
    
    Fixes #474
Commits on Sep 26, 2014
  1. @grosser @latortuga

    do not double-escape test names

    grosser committed with latortuga
Commits on Sep 24, 2014
  1. @latortuga

    Merge pull request #485 from rcook/p-rcook-minitest-exit-hooks

    latortuga committed
    Fix Minitest exit hook hack to handle Minitest 5
Something went wrong with that request. Please try again.