09 Jan, 2014
1 commit
-
- Added a field on article new/edit to specify which users can access the article - Added a relationship has_and_belongs_to_many between Article and Person - Created a new table article_privacy_exceptions for has_and_belongs_to_many - Added cucumber tests - Added a new cucumber step to add a user to the exception users list (ActionItem2852) Signed-off-by: Alex de Souza <campelo.al1@gmail.com> Signed-off-by: Athos Ribeiro <athoscribeiro@gmail.com> Signed-off-by: Andre Bedran <bedran.fleck@gmail.com> Signed-off-by: Arthur Del Esposte <arthurmde@gmail.com> Signed-off-by: Carlos Andre <carlos.andre.souza@msn.com> Signed-off-by: Fabio Teixeira <fabio1079@gmail.com> Signed-off-by: Gabriela Navarro <navarro1703@gmail.com> Signed-off-by: Gustavo Jaruga <darksshades@hotmail.com> Signed-off-by: Matheus Faria <matheus.sousa.faria@gmail.com> Signed-off-by: Tales Martins <tales.martins@gmail.com>
12 Dec, 2013
1 commit
-
(ActionItem2849) Signed-off-by: Marcos Ramos <ms.ramos@outlook.com Signed-off-by: Valéssio Brito <contato@valessiobrito.com.br> Signed-off-by: Victor Hugo Alves de Carvalho <victorhugodf.ac@gmail.com>
03 Oct, 2013
1 commit
20 Aug, 2013
1 commit
17 Jul, 2013
1 commit
22 May, 2013
1 commit
-
Moving solr specifics to the plugin
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
21 commits
-
Conflicts: plugins/mezuro/public/javascripts/project_content.js
27 Mar, 2013
1 commit
26 Mar, 2013
1 commit
21 Mar, 2013
4 commits
-
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.
20 Mar, 2013
1 commit
-
…into merge-requests/267 Conflicts: features/signup.feature features/step_definitions/noosfero_steps.rb Making tests on signup wait for the bot trap time and use selenium.
18 Mar, 2013
1 commit
05 Mar, 2013
2 commits
04 Mar, 2013
1 commit
25 Feb, 2013
1 commit