-
Notifications
You must be signed in to change notification settings - Fork 646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: failing test for assigned_article_spec #6063
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,6 +23,8 @@ | |
visit "/courses/#{course.slug}/articles/assigned" | ||
expect(page).to have_content('Nancy Tuana') | ||
find('a', text: 'Feedback').click | ||
expect(page).to have_no_content(I18n.t('courses.feedback_loading')) | ||
expect(page).to have_selector('textarea.feedback-form') | ||
find('textarea.feedback-form').fill_in with: 'This is a great article!' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The issue i am working on is that the textarea.feedback-form is not rendered imidiatle, because all the users suggestions for that course has to be loaded which takes a bit longer that the normal wait time of Capybara, so the test fails even before the textarea.feedback-form is rendered, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The normal wait time for Capybara is pretty long, and we rarely need to wait longer. I think the issue here is that |
||
click_button 'Add Suggestion' | ||
find('a', text: 'Delete').click | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's this for? It doesn't seem to be used directly by the code you've changed. If it's unrelated to fixing the spec, then at minimum it should be done in a separate commit with an explanation in the commit message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for courses with no ratings it throughs an error, of missing.en.does_not_exist because the en.yml file does not contain a defintion for does_not_exist under courses