fed82b0024
Until now, when institutions made custom changes which made certain tests obsolete, they didn't have a clear way to deal with the failing tests. They would either: 1. Stop running the test suite 2. Run the test suite and get test failures 100% of the time 3. Comment the failing tests 4. Modify the failing tests in order to keep them in sync with the code Solution 1 would be suicide from a maintenance perspective, although it could work if only a couple of small custom changes were done. Solution 2 would make it really hard to differenciate between "false failures" and "real failures" when running the test suite. Solution 3 would cause many conflicts when updating to a newer version of Consul. Solution 4 could make sense sometimes (big tests where only one line needs to be changed), but it would also cause conflicts when updating Consul. So now, we're giving an alternative to solution 3 by making it easier to exclude a test. For tests that still need to be changed, when to use this solution combined with a custom test and when to use solution 4 will have to be decided on a per-case basis.
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.7.4, CMake, pkg-config, shared-mime-info, Node.js and PostgreSQL (>=9.5).
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