help-libidn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: testing Context O/J


From: Abdulrahman I. ALGhadir
Subject: RE: testing Context O/J
Date: Sat, 16 Apr 2011 06:03:21 +0000

Hey again,
Sorry it took me awhile to do the test due the fact I was abit busy back then.
When I was trying to compile the test-lookup.c with a set of examples of 
existent domains I got this error msg:
expected rc 0 got rc -206

I have attached the file in case you want to see them.

Abdulrahman,

-----Original Message-----
From: Simon Josefsson [mailto:address@hidden 
Sent: 30/Mar/2011 10:47 AM
To: Abdulrahman I. ALGhadir
Cc: address@hidden
Subject: Re: testing Context O/J

"Abdulrahman I. ALGhadir" <address@hidden> writes:

> Dear Simon,
> I am Abdulrahman from SaudiNIC and I am willing to help in testing the
> part which is related to Context O/J for R2L languages such as Arabic.
> I am going to inform you with details but do you have certain
> scenarios in your mind for test or just do my best?

Hi Abdulrahman, and welcome!  Your help is really important, I don't
have your expertise.

What would help if you have a bunch (say 10-20) common R2L domains to
make sure we don't introduce any serious regressions.  You want to add
them to tests/test-lookup.c like the following:

static const struct idna idna[] = {
...
  {"\xe6\xb5\x8b\xe8\xaf\x95", "xn--0zwm56d" },

The first string is escaped UTF-8 and the second is the ACE encoding.

Second, and perhaps more challenging, is to prepare real corner-case
test vectors that triggers the IDNA2008 rules related to CONTEXT O/J and
BIDI rules.  What we would want is to make sure all paths in the code is
tested.

I'm going to prepare code coverage charts for libidn2, which would help
to identify which parts needs testing -- that will help us find the
necessary test vectors.

/Simon

-----------------------------------------------------------------------------------
Disclaimer:
This message and its attachment, if any, are confidential and may contain 
legally
privileged information. If you are not the intended recipient, please contact 
the
sender immediately and delete this message and its attachment, if any, from your
system. You should not copy this message or disclose its contents to any other
person or use it for any purpose. Statements and opinions expressed in this 
e-mail
are those of the sender, and do not necessarily reflect those of the 
Communications
and Information Technology Commission (CITC). CITC accepts no liability for 
damage
caused by this email.

Attachment: test-lookup.c
Description: test-lookup.c


reply via email to

[Prev in Thread] Current Thread [Next in Thread]