The test was hanging sometimes on my machine, probably because we weren't making sure the request submitting the form had finished before visiting a new page. In theory the spec should have been fine from a technical point of view: since submitting the form generates a regular HTTP request (and not an AJAX one), Capybara/Selenium/Chromedrive should wait until the request is finished. But that doesn't seem to be the case 100% of the time; maybe conditions change depending on previous tests. On the other hand, from a design point of view, the spec wasn't that fine. The main purpose of system specs is to test the way users interact with our application, and users don't click a button and immediately visit a different page. Instead, most users wait until they receive feedback of their actions, and then they visit a different page. Of course some users might visit another page without waiting. What happens then cannot be predicted (it will depend on which request is handled first), and so there's no point in writing a test for this case unless there's a specific concurrency issue we'd like to check.
CONSUL
Citizen Participation and Open Government Application
This is the opensource code repository of the eParticipation website CONSUL, originally developed for the Madrid City government eParticipation website
Documentation
Check the ongoing documentation at https://docs.consulproject.org to learn more about how to start your own CONSUL fork, install it, customize it and learn to use it from an administrator/maintainer perspective.
CONSUL Project main website
You can access the main website of the project at http://consulproject.org where you can find documentation about the use of the platform, videos, and links to the community space.
Configuration for development and test environments
NOTE: For more detailed instructions check the docs
Prerequisites: install git, Ruby 2.6.6, CMake, pkg-config, Node.js and PostgreSQL (>=9.4).
git clone https://github.com/consul/consul.git
cd consul
bundle install
cp config/database.yml.example config/database.yml
cp config/secrets.yml.example config/secrets.yml
bin/rake db:create
bin/rake db:migrate
bin/rake db:dev_seed
RAILS_ENV=test rake db:setup
Run the app locally:
bin/rails s
Run the tests with:
bin/rspec
You can use the default admin user from the seeds file:
user: admin@consul.dev pass: 12345678
But for some actions like voting, you will need a verified user, the seeds file also includes one:
user: verified@consul.dev pass: 12345678
Configuration for production environments
See installer
Current state
Development started on 2015 July 15th. Code was deployed to production on 2015 september 7th to decide.madrid.es. Since then new features are added often. You can take a look at the current features at the project's website and future features at the Roadmap and open issues list.
License
Code published under AFFERO GPL v3 (see LICENSE-AGPLv3.txt)
Contributions
See CONTRIBUTING.md
