mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-06-26 05:00:28 +02:00
e33dd7bfd8
fr_FR was mostly being tested as an 8-bit locale. This changes
the tests to focus on fr_FR.utf8. But it adds a section for fr_FR 8-bit
currency. Divergence in vendor-supplied locales often occurs
in currency.
MINGW, which only handles 8-bit locales when using MSVCRT, was being tested
as if its 8-bit CP1252 locale was UTF-8. While the tests were included
as better than nothing, it is technically incorrect. These tests are
no longer run. Soon, Guile's MINGW build will link to UCRT, and it will
have UTF-8 locales.
The responses for some tests were modified to allow reasonable responses
from Cygwin/MSYS/MinGW locales and to skip on unreasonable responses.
* test-suite/tests/i18n.test (mingw?): rename to old-ms?
(old-ms?): new helper
(%french-locale-name): use platform's default 8-bit locale
(%french-utf8-locale-name, %turkish-utf8-locale-name, %german-utf8-locale-name)
(%greek-utf8-locale-name): don't use 8-bit locales on MINGW
("text collation (French)"): use utf-8
("locale-digit-grouping (French)"): use utf-8
(french-number-string=?): modify to make symmetric and to handle
U+2024 as a valid spacer
("French: integer", "negative integer" "fraction", "fraction, 1 digit"):
("French"): rename to "French UTF-8"
("French UTF-8: 12345.678", "Fraction"): use utf-8, allow U+2024
("French UTF-8: positive inexact zero"): expect euro sign
("French 8-bit"): new currency tests
|
||
|---|---|---|
| .. | ||
| lalr | ||
| standalone | ||
| test-suite | ||
| tests | ||
| ChangeLog-2008 | ||
| driver | ||
| guile-test | ||
| Makefile.am | ||
| README | ||
This directory contains some tests for Guile, and some generic test support code. To run these tests, you will need a version of Guile more recent than 15 Feb 1999 --- the tests use the (ice-9 and-let*) and (ice-9 getopt-long) modules, which were added to Guile around then. For information about how to run the test suite, read the usage instructions in the comments at the top of the guile-test script. You can reference the file `lib.scm' from your own code as the module (test-suite lib); it also has comments at the top and before each function explaining what's going on. Please write more Guile tests, and send them to bug-guile@gnu.org. We'll merge them into the distribution. All test suites must be licensed for our use under the GPL, but I don't think I'm going to collect assignment papers for them. Some test suite philosophy: GDB has an extensive test suite --- around 6300 tests. Every time the test suite catches a bug, it's great. GDB is so complicated that folks are often unable to get a solid understanding of the code before making a change --- we just don't have time. You'll see people say things like, "Here's a fix for X; it doesn't cause any regressions." The subtext is, I made a change that looks reasonable, and the test suite didn't complain, so it must be okay. I think this is terrible, because it suggests that the writer is using the test suite as a substitute for having a rock-solid explanation of why their changes are correct. The problem is that any test suite is woefully incomplete. Diligent reasoning about code can catch corner conditions or limitations that no test suite will ever find. Jim's rule for test suites: Every test suite failure should be a complete, mysterious surprise, never a possibility you were prepared for. Any other attitude indicates that you're using the test suite as a crutch, which you need only because your understanding is weak.