Fix Flaky Tests / Optimize Checking of plan.title
Within spec/features/plans/exports_spec.rb
#3451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3450
Changes proposed in this PR:
spec/features/plans/exports_spec.rb
(see Some Selenium/Features Tests Breaking (Independent of Code Changes) #3450)expect(page.source).to have_text(plan.title)
sometimes failed because sometimespage.source == ""
.page.source
, which returns the entire HTML content of the page, this PR usespage.title
, which only returns the contents inside of the<title>
tags.page.title
does not seem to encounter the unwanted behaviour of returning a blank string. Maybe because it is faster (only returning the title should be faster than returning the entire HTML content viapage.source
)?<title>
title tags and their contents are part of the entire HTML content. So despitepage.source
returning a blank string, becausepage.title
is not blank, it follows that the DOM is not blank.