12 Aug, 2015

1 commit

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

  • 932e054f   Add support for base plugins ... Browse File » 
    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

  • dda93504   Improve plugin test runs ... Browse File » 
    - 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

  • 29866897   Allowing plugins to extend cucumber steps and support ... Browse File » 
    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

3 commits

21 Dec, 2011

1 commit

  • 1782ed45   Make plugins tests run correctly ... Browse File » 
    The fact that tables matching /_plugin_/ were being excluded from
db/schema.rb broke the tests, because the test database was being
created without the necessary tables. And db/schema.rb was already not
left untouched anyway, since several plugins add columns to existing
Noosfero tables ...
    Antonio Terceiro
     

10 Aug, 2011

1 commit

  • 6ccec5a4   Plugins test tasks ... Browse File » 
      * Fixing 'available' task. This task was running only the enabled
    plugins. Now, before running this task, all plugins are enabled and
    after, the ones that were disabled are disabled again.
  * Running plugins tests on noosfero rake with all other tests.
    Rodrigo Souto
     

10 May, 2011

1 commit