| Title: | P4DTI automated testing with Unicode data is poor |
| Status: | closed |
| Priority: | essential |
| Assigned user: | Nick Barnes |
| Organization: | Ravenbrook |
| Description: | The P4DTI now replicates Unicode data satisfactorily, but the automated testing of this feature is inadequate: only testing operation with and without Unicode-mode Perforce servers. |
| Analysis: | The automated test suite should have a "unicode" switch for several of its tests. When the switch is on, comments added to Bugzilla bugs or Perforce jobs during the test should include non-ASCII Unicode characters from several differnt code charts (although note that non-BMP characters are not yet supported by MySQL). The test suite should automatically run tests with the switch off and with it on. |
| How found: | inspection |
| Evidence: | I just know |
| Observed in: | 2.4.3 |
| Introduced in: | 2.4.3 |
| Test procedure: | test_p4dti.py unicode, test_p4dti.py unicode_lifecycle |
| Created by: | Nick Barnes |
| Created on: | 2009‑04‑14 13:25:50 |
| Last modified by: | Nick Barnes |
| Last modified on: | 2009‑04‑14 13:26:16 |
| History: | 2009-04-14 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 167771 | closed | 2009‑04‑14 12:48:37 | Nick Barnes | Improve MySQL version detection, Unicode configuration detection, Unicode replication testing, and error handling in the presence of Unicode strings. |
Generated at 2013-05-22 17:06:10 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#476 $
Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.