It's true that the test cases can be split into an ASCII portion and an IDN portion, and our guidance can show people how to start with one and work to the other. But we should be very careful not to imply that ASCII-only is "good enough". -----Original Message----- From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Ronald Geens Sent: Wednesday, December 30, 2015 6:15 AM To: UA-discuss@icann.org Subject: Re: [UA-discuss] Use Cases Rubens, I fully agree that test processes should indeed be fully automated … in reality there are still a lot of cases, especially in front-end and website development I am afraid, where this is not the case. Anyhow, it is not only the testing cost that will determine which usecases to support for a certain development. Splitting the usecases into two levels would already allow a working solution at minimal level without having "to bother" with IDN development and testing. This is of course a very much ASCII-world driven viewpoint which is not necessarily in line with real Universal Acceptance but using the agile principle of “good enough” this still has value according to me. Ron Geens DNS Belgium
On 30 Dec 2015, at 13:09, Rubens Kuhl <rubensk@nic.br> wrote:
Em 30 de dez de 2015, à(s) 09:28:000, Ronald Geens <ronald.geens@dnsbelgium.be> escreveu:
I haven’t seen any replies yet but as I think it is an important topic I would like to chime in.
In theory all of the cases mentioned below should be tested but as you indicated this is cost prohibitive.
I disagree that cost is linked to the number of test cases. Test processes today are usually automated, so lifecycle management is usually the main cost driver, no matter testing 10 or 20 use cases.
Rubens