22 Apr, 2016

1 commit


20 Apr, 2016

1 commit


06 Apr, 2016

1 commit


22 Mar, 2016

2 commits


12 Mar, 2016

2 commits


28 Jan, 2016

1 commit


28 Dec, 2015

1 commit


09 Nov, 2015

1 commit


02 Oct, 2015

1 commit


29 Sep, 2015

1 commit


13 Aug, 2015

1 commit


12 Aug, 2015

1 commit


24 Jul, 2015

1 commit

  • Use these two commands inside vim:
    :!ag -l '..\/..\/..\/..\/test' | xargs perl -pi -E "s/require.*test_helper.*/require 'test_helper'/g"
    :!ag -l "require File.*'/" | xargs perl -pi -E "s/require File.*'\//require_relative '/g":e ""'"
    Braulio Bhavamitra
     

25 Mar, 2015

1 commit


24 Feb, 2015

1 commit


28 Jan, 2015

2 commits


15 Dec, 2014

1 commit


12 Dec, 2014

1 commit


09 Dec, 2014

1 commit


08 Dec, 2014

1 commit


04 Dec, 2014

1 commit


27 Nov, 2014

1 commit


19 Nov, 2014

1 commit


05 Nov, 2014

1 commit


30 Jul, 2014

1 commit

  • Base plugins are enanbed by default and cannot be disabled at the system
    level, but can be disabled per-environment at the web UI.
    
    A part of the required changes also fix the Noosfero plugin
    infrastructure, in special migrations, on Rails 3.
    Antonio Terceiro
     

28 Jul, 2014

1 commit

  • - process plugins in alphabeticall order, so when watching the console
      output, one can know at which point of the execution we are.
    - run all tests of a given type (unit, functional etc) for a single
      plugin together. On my machine this brings the total run time from
      ~34min down to ~20min.
    Antonio Terceiro
     

08 Apr, 2014

1 commit


31 Mar, 2014

1 commit


03 Apr, 2013

1 commit

  • Now the plugins can create the folders 'step_definitions' and 'support'
    under the folder 'features' to extend cucumber features as it pleases.
    
    The plugins with any extension gain 2 new profiles on the cucumber.yml
    file. For example, for mezuro plugin, it will have the 'mezuro' and
    'mezuro_selenium' cucumber profiles that will load the appropriate
    files. So if you extend cucumber with new steps, hooks, etc; and you
    want to run the cucumber tests of mezuro plugin with all these
    extensions you must include '-p mezuro' on the cucumber call (or '-p
    mezuro-selenium' to run selenium profile). This is already handled by
    the rake task that runs the plugins' tests. So it'd be much better to
    run 'rake test:noosfero_plugins:mezuro:{cucumber,selenium}' instead.
    
    Also:
       * Moving plugins' 'features' folder to the plugin' root instead of
         inside the folder 'test' (just following Rails convention).
       * Moving specific steps and hooks of mezuro from core to the plugin.
       * Requiring plugin to be enabled to run any of its tests.
    Rodrigo Souto
     

07 Mar, 2013

1 commit


06 Mar, 2013

1 commit


28 Aug, 2012

3 commits


27 Feb, 2012

1 commit


09 Feb, 2012

1 commit


31 Jan, 2012

1 commit