-
Notifications
You must be signed in to change notification settings - Fork 1k
More test fixes for when translations are present #7478
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
Conversation
capture.output() tests are fine in many places, but these ones tested for messages that have since been translated and must be skipped in foreign more.
Where capture.output() was previously used to test the absence of messages, use notOutput= instead so that the test will be skipped. While the test succeeded anyway due to the captured output containing neither the original untranslated message (being matched) nor its translation (that could be printed if a regression happened), skipping the test is more fair.
When working in foreign mode, count the occurrences of tests for message content (which are essentially skipped) and report the number if it's non-zero.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7478 +/- ##
=======================================
Coverage 99.06% 99.06%
=======================================
Files 86 86
Lines 16618 16629 +11
=======================================
+ Hits 16463 16474 +11
Misses 155 155 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
No obvious timing issues in HEAD=more-foreign-tests Generated via commit 01857cb Download link for the artifact containing the test results: ↓ atime-results.zip
|
MichaelChirico
left a comment
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.
Great!!
Instead, test substitute(x) for %iscall% "print" to decide whether to print the x before testing the output.

Switch all tests that depend on untranslated output being produced to use
output=ornotOutput=so that translation doesn't break them any more. Skip test 1590.14 because it fails due to the bytes having completely different meanings on Windows when the ANSI codepage is not 1252.This will still fail in interesting ways (e.g.
translateChar()warnings from the parser) on systems that cannot represent Latin-1 characters in the native encoding. We still need #7388 and a few more fixes for that.