16 Jul, 2013

2 commits


15 Jul, 2013

6 commits


13 Jul, 2013

2 commits


12 Jul, 2013

1 commit


11 Jul, 2013

1 commit


08 Jul, 2013

2 commits


28 Jun, 2013

1 commit


27 Jun, 2013

1 commit


18 Jun, 2013

1 commit


29 May, 2013

1 commit


28 May, 2013

2 commits


23 May, 2013

1 commit


21 May, 2013

3 commits


20 May, 2013

2 commits


15 May, 2013

1 commit


13 May, 2013

1 commit


09 May, 2013

1 commit


08 May, 2013

5 commits


07 May, 2013

1 commit


24 Apr, 2013

1 commit


20 Apr, 2013

1 commit


17 Apr, 2013

2 commits


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