ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Yury G. Kudryashov" <urkud@ya.ru>
To: ntg-context@ntg.nl
Subject: Re: ConTeXt unit testing
Date: Sun, 06 Jun 2010 15:12:09 +0400	[thread overview]
Message-ID: <hufvq9$8pd$1@dough.gmane.org> (raw)
In-Reply-To: <4C0B7A6E.1030801@elvenkind.com>

Taco Hoekwater wrote:

> Mojca Miklavec wrote:
>> On Sun, Jun 6, 2010 at 11:05, Taco Hoekwater wrote wrote:
>>> Mojca Miklavec wrote:
>>>> On Sat, Jun 5, 2010 at 17:13, Yury G. Kudryashov wrote:
>>>>> Are there any automatic unit test for ConTeXt distribution?
>>>> I'm thinking that we might want to set up one on a server.
>>> We already have a server for tests:
>>>
>>>  http://foundry.supelec.fr/gf/project/contexttest/
>> 
>> Yes, but some metadata is missing and some architecture to actually
>> run those tests (some tests only make sense in MKII and some only in
>> MKIV etc.).
>> 
>> I would definitely prefer if some function "run_the_unit_tests"
>> existed, but we probably need to write one first.
> 
> Just saying there is no need for yet another server  (you cannot
> run tests server-side anyway).

Why? I was talking about fully automatic tests, not tests like "compile and 
open result in the viewer". I understand that there is not too much 
functionality that can be tested automatically (hence, server-side), but at 
least some basic things can be tested.

Probably, more features can be tested server-side analyzing the result pdf 
file using some library (though I don't know the pdf-parsing libraries 
sufficiently good to implement it).

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-06-06 11:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 15:13 Yury G. Kudryashov
2010-06-05 15:43 ` Mojca Miklavec
2010-06-05 16:14   ` Otared Kavian
2010-06-05 19:05 ` luigi scarso
2010-06-06  8:51 ` Mojca Miklavec
2010-06-06  9:05   ` Taco Hoekwater
2010-06-06  9:14     ` Mojca Miklavec
2010-06-06 10:37       ` Taco Hoekwater
2010-06-06 11:12         ` Yury G. Kudryashov [this message]
2010-06-06 11:14           ` Taco Hoekwater
2010-06-06 11:53             ` Peter Münster
2010-06-06 11:54               ` Taco Hoekwater
2010-06-06 11:51           ` Peter Münster
2010-06-06 11:53             ` Taco Hoekwater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hufvq9$8pd$1@dough.gmane.org' \
    --to=urkud@ya.ru \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).