Having a class named `Poll::Question::Answer` and another class named `Poll::Answer` was so confusing that no developer working on the project has ever been capable of remembering which is which for more than a few seconds. Furthermore, we're planning to add open answers to polls, and we might add a reference from the `poll_answers` table to the `poll_question_answers` table to property differentiate between open answers and closed answers. Having yet another thing named answer would be more than what our brains can handle (we know it because we did this once in a prototype). So we're renaming `Poll::Question::Answer` to `Poll::Question::Option`. Hopefully that'll make it easier to remember. The name is also (more or less) consistent with the `Legislation::QuestionOption` class, which is similar. We aren't changing the table or columns names for now in order to avoid possible issues when upgrading (old code running with the new database tables/columns after running the migrations but before deployment has finished, for instance). We might do it in the future. I've tried not to change the internationalization keys either so existing translations would still be valid. However, since we have to change the keys in `activerecord.yml` so methods like `human_attribute_name` keep working, I'm also changing them in places where similar keys were used (like `poll_question_answer` or `poll/question/answer`). Note that it isn't clear whether we should use `option` or `question_option` in some cases. In order to keep things simple, we're using `option` where we were using `answer` and `question_option` where we were using `question_answer`. Also note we're adding tests for the admin menu component, since at first I forgot to change the `answers` reference there and all tests passed.
62 lines
2.1 KiB
Ruby
62 lines
2.1 KiB
Ruby
require "rails_helper"
|
|
|
|
describe "Poll Results" do
|
|
scenario "List each Poll question" do
|
|
user1 = create(:user, :level_two)
|
|
user2 = create(:user, :level_two)
|
|
user3 = create(:user, :level_two)
|
|
|
|
poll = create(:poll, results_enabled: true)
|
|
question1 = create(:poll_question, poll: poll)
|
|
answer1 = create(:poll_question_option, question: question1, title: "Yes")
|
|
answer2 = create(:poll_question_option, question: question1, title: "No")
|
|
|
|
question2 = create(:poll_question, poll: poll)
|
|
answer3 = create(:poll_question_option, question: question2, title: "Blue")
|
|
answer4 = create(:poll_question_option, question: question2, title: "Green")
|
|
answer5 = create(:poll_question_option, question: question2, title: "Yellow")
|
|
|
|
login_as user1
|
|
vote_for_poll_via_web(poll, question1, "Yes")
|
|
vote_for_poll_via_web(poll, question2, "Blue")
|
|
logout
|
|
|
|
login_as user2
|
|
vote_for_poll_via_web(poll, question1, "Yes")
|
|
vote_for_poll_via_web(poll, question2, "Green")
|
|
logout
|
|
|
|
login_as user3
|
|
vote_for_poll_via_web(poll, question1, "No")
|
|
vote_for_poll_via_web(poll, question2, "Yellow")
|
|
logout
|
|
|
|
travel_to(poll.ends_at + 1.day)
|
|
|
|
visit results_poll_path(poll)
|
|
|
|
expect(page).to have_content(question1.title)
|
|
expect(page).to have_content(question2.title)
|
|
|
|
within("#question_#{question1.id}_results_table") do
|
|
expect(find("#answer_#{answer1.id}_result")).to have_content("2 (66.67%)")
|
|
expect(find("#answer_#{answer2.id}_result")).to have_content("1 (33.33%)")
|
|
end
|
|
|
|
within("#question_#{question2.id}_results_table") do
|
|
expect(find("#answer_#{answer3.id}_result")).to have_content("1 (33.33%)")
|
|
expect(find("#answer_#{answer4.id}_result")).to have_content("1 (33.33%)")
|
|
expect(find("#answer_#{answer5.id}_result")).to have_content("1 (33.33%)")
|
|
end
|
|
end
|
|
|
|
scenario "Results for polls with questions but without answers" do
|
|
poll = create(:poll, :expired, results_enabled: true)
|
|
question = create(:poll_question, poll: poll)
|
|
|
|
visit results_poll_path(poll)
|
|
|
|
expect(page).to have_content question.title
|
|
end
|
|
end
|