Ruby on Rails Electoral Project
Budget: £250 – £750 GBP
Hi,
I am making an Election Ruby on Rails 7 app. The election app should run some electoral algorithms (I will specify which when accepted). The project has already been started so I will give you a git repo and branch to start making your modifications.
There are 3 users
• Admin: normal admin privileges
• Host: This is the Host of the ballot
• Voter: This is the voter on a given ballot
How it works
• Host:
• On account creation the Host should be able to create new ballots.
o Ballots have the following parameters
user_id", null: false
t.string "title"
t.datetime "start_date"
t.datetime "end_date"
• In the ballot the host should be able to add new questions and create x number of options for those questions.
• To start a ballot the host should be able to launch the ballot immediately
OR
Schedule the ballot based on the start_time
• Voter:
o Voters would be directed to a page where they will need to enter the ballot access_token to enter the assigned ballot.
o After this, they should be prompted to input a username or generate a username to be used within the ballot
o If the ballot has launched(so the start time has elapsed OR the ballot has been force launched by the host) the questions should be rendered on the voter’s screens.
o If the ballot has not yet been launched display a message saying that the ballot has not started, give the start date and end date of the ballot and provide the host’s email address to the user.
Requirements :
• Frequent git commits so I can see the changes
• You must work on the branch given.
o Git semantics must be used:
feat: (new feature for the user, not a new feature for build script)
fix: (bug fix for the user, not a fix to a build script)
docs: (changes to the documentation)
style: (formatting, missing semi colons, etc; no production code change)
refactor: (refactoring production code, eg. renaming a variable)
test: (adding missing tests, refactoring tests; no production code change)
chore: (updating grunt tasks etc; no production code change)
• RSPEC using factory_bot for tests
o Test the following rspec paths
spec/models
spec/features
spec/requests
I am making an Election Ruby on Rails 7 app. The election app should run some electoral algorithms (I will specify which when accepted). The project has already been started so I will give you a git repo and branch to start making your modifications.
There are 3 users
• Admin: normal admin privileges
• Host: This is the Host of the ballot
• Voter: This is the voter on a given ballot
How it works
• Host:
• On account creation the Host should be able to create new ballots.
o Ballots have the following parameters
user_id", null: false
t.string "title"
t.datetime "start_date"
t.datetime "end_date"
• In the ballot the host should be able to add new questions and create x number of options for those questions.
• To start a ballot the host should be able to launch the ballot immediately
OR
Schedule the ballot based on the start_time
• Voter:
o Voters would be directed to a page where they will need to enter the ballot access_token to enter the assigned ballot.
o After this, they should be prompted to input a username or generate a username to be used within the ballot
o If the ballot has launched(so the start time has elapsed OR the ballot has been force launched by the host) the questions should be rendered on the voter’s screens.
o If the ballot has not yet been launched display a message saying that the ballot has not started, give the start date and end date of the ballot and provide the host’s email address to the user.
Requirements :
• Frequent git commits so I can see the changes
• You must work on the branch given.
o Git semantics must be used:
feat: (new feature for the user, not a new feature for build script)
fix: (bug fix for the user, not a fix to a build script)
docs: (changes to the documentation)
style: (formatting, missing semi colons, etc; no production code change)
refactor: (refactoring production code, eg. renaming a variable)
test: (adding missing tests, refactoring tests; no production code change)
chore: (updating grunt tasks etc; no production code change)
• RSPEC using factory_bot for tests
o Test the following rspec paths
spec/models
spec/features
spec/requests