W3C home > Mailing lists > Public > public-i18n-arabic@w3.org > January to March 2018

Creating tests for gap analysis or other reasons

From: r12a <ishida@w3.org>
Date: Thu, 22 Feb 2018 09:42:07 +0000
To: Najib Tounsi <ntounsi@emi.ac.ma>
Cc: public-i18n-arabic@w3.org
Message-ID: <cb8ea46d-10ae-0ac2-0fb1-35c267024d5e@w3.org>
hi Najib,

following up on your question during Tuesday's telecon...

I have been updating the Japanese gap analysis doc, and yesterday i 
added some tests.  You could use these as a model for the tests you want 
to create.

Go to https://w3c.github.io/jlreq/gap-analysis/#transforms

There are two types of test page pointed to:

[1] Tests: standard syntax • proprietary syntax

This is a simple format that i use for my articles on vertical text, 
ruby, etc.  It shows the relevant code when the page is displayed.

[2] More tests: a-z, A-Z, punctuation, katakana, punctuation, symbols

These are tests in the Web Platform Tests format. (When i get time, i'll 
add them to the i18n framework and WPT repo.)  The format for those 
tests is described at http://web-platform-tests.org/ (Writing tests)

Note that these tests check behaviour for a number of characters all on 
the same page. I think this is desirable for this kind of test, where 
many characters are being tested. However, normally each test page would 
test a single thing.

I hope that helps give you some ideas about how to proceed.


PS: Shervin, Behnam, i've been taking the japanese gap analysis a bit 
further than the others, so you may like to look at what i've done. It 
still needs plenty more work – i only spent a short time on it.
Received on Thursday, 22 February 2018 09:42:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:55:32 UTC