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.
02 Apr, 2013
8 commits
-
…ibro source code repository
-
Conflicts: plugins/mezuro/public/javascripts/project_content.js
27 Mar, 2013
2 commits
21 Mar, 2013
1 commit
-
Some tests were breaking because since Selenium Driver 2, hidden elements aren't available for interaction. However some elements started to get unaccessible because some depend on hover on other elements and the current version of Capybara doesn't support hover yet. Avoid interaction with hidden elements is nice, but for the sake of having the tests running while there isn't any touchable way of displaying those elements through adequate methods, I'm overriding this behaviour of Selenium Driver 2 with: Capybara.ignore_hidden_elements = true.
05 Mar, 2013
1 commit
04 Mar, 2013
1 commit
13 Dec, 2012
1 commit
12 Dec, 2012
1 commit
10 Dec, 2012
16 commits
07 Dec, 2012
1 commit
29 Nov, 2012
1 commit
24 Nov, 2012
2 commits
23 Nov, 2012
4 commits