📅 Original date posted:2014-06-14
📝 Original message:Not when failure is defined as, e.g., extra text pushing a UI element
down such that the button the user needs to click is no longer visible.
You don't test that except by having a human being run through some
example workflows, which is presumably happening during the release process.
On 06/13/2014 10:58 PM, Un Ix wrote:
> Was joking, but isn't the translation process back-ended with runtime
> tests to ensure that any stray chars etc cause the application to
> fail?
>
>> On 14/06/2014, at 1:49 pm, "Matt Whitlock" <bip at mattwhitlock.name>
>> wrote:
>>
>>> On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote: How about a
>>> prize for anyone who can spot any "malicious" strings within next
>>> hour?
>>
>> I think it's more an issue of accidental breakage than any
>> maliciousness. One character in the wrong place in a language
>> bundle somewhere can make the difference between success and
>> runtime failure, and it may not be immediately apparent when
>> running in unaffected locales. This kind of problem isn't likely to
>> result in data loss (or money loss, where money is data, is in
>> Bitcoin), but it could be enough to necessitate scrapping the whole
>> release, which would look bad and prompt users to question the dev
>> team's quality control process.
>
Mark Friedenbach [ARCHIVE] /
npub1r3…48d0u
2023-06-07 15:22:39
in reply to nevent1q…cyhc
Author Public Key
npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0uPublished at
2023-06-07 15:22:39Event JSON
{
"id": "be79672785f5e36db34fc3a133e30124021d6d1dbdf97fbba9b66a60540d3d41",
"pubkey": "1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069",
"created_at": 1686151359,
"kind": 1,
"tags": [
[
"e",
"a7227de8a6e97c1dbd351d4724658eec4042be0f772d051e197a562ef93f0d92",
"",
"root"
],
[
"e",
"6b387d46f2115d8af5f93f11e339287837de11834505c8dfc74c653ad91f535d",
"",
"reply"
],
[
"p",
"d988713728aacd73c33ee22c34dc8971b2c821181e33523773b0b419aa921386"
]
],
"content": "📅 Original date posted:2014-06-14\n📝 Original message:Not when failure is defined as, e.g., extra text pushing a UI element\ndown such that the button the user needs to click is no longer visible.\nYou don't test that except by having a human being run through some\nexample workflows, which is presumably happening during the release process.\n\nOn 06/13/2014 10:58 PM, Un Ix wrote:\n\u003e Was joking, but isn't the translation process back-ended with runtime\n\u003e tests to ensure that any stray chars etc cause the application to\n\u003e fail?\n\u003e \n\u003e\u003e On 14/06/2014, at 1:49 pm, \"Matt Whitlock\" \u003cbip at mattwhitlock.name\u003e\n\u003e\u003e wrote:\n\u003e\u003e \n\u003e\u003e\u003e On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote: How about a\n\u003e\u003e\u003e prize for anyone who can spot any \"malicious\" strings within next\n\u003e\u003e\u003e hour?\n\u003e\u003e \n\u003e\u003e I think it's more an issue of accidental breakage than any\n\u003e\u003e maliciousness. One character in the wrong place in a language\n\u003e\u003e bundle somewhere can make the difference between success and\n\u003e\u003e runtime failure, and it may not be immediately apparent when\n\u003e\u003e running in unaffected locales. This kind of problem isn't likely to\n\u003e\u003e result in data loss (or money loss, where money is data, is in\n\u003e\u003e Bitcoin), but it could be enough to necessitate scrapping the whole\n\u003e\u003e release, which would look bad and prompt users to question the dev\n\u003e\u003e team's quality control process.\n\u003e",
"sig": "125a7a3cf509267af1690dce29f2f5d3b1cec12af2e363017f07a8fd6f182bb8395ff66ebd01a254ebe3e9f3d63648417e6eb1054427165d36b6220240354c18"
}