[ruby/syntax_suggest] Change assertion to not rely on exact text from prism

The original ripper test was very stable as the output didn't change. Prism is under active development and changing their output shouldn't cause a failure to the ruby/ruby test suite like https://github.com/ruby/ruby/actions/runs/7104601478/job/19339940315.

This commit moves from checking exact output to asserting that the string we get back is not empty. This should give the same level of confidence that some error message was caught, and is less brittle.

https://github.com/ruby/syntax_suggest/commit/4b6abb763e
This commit is contained in:
Schneems 2023-12-05 12:24:06 -06:00 коммит произвёл git
Родитель a063969ec1
Коммит 82883dc8f2
1 изменённых файлов: 1 добавлений и 5 удалений

Просмотреть файл

@ -14,11 +14,7 @@ module SyntaxSuggest
).call
expect(explain.missing).to eq([])
if SyntaxSuggest.use_prism_parser?
expect(explain.errors.join).to include("Expected a closing delimiter for the interpolated string")
else
expect(explain.errors.join).to include("unterminated string")
end
expect(explain.errors.join.strip).to_not be_empty
end
it "handles %w[]" do