ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt unit testing
Date: Sun, 06 Jun 2010 13:14:09 +0200	[thread overview]
Message-ID: <4C0B8301.3020100@elvenkind.com> (raw)
In-Reply-To: <hufvq9$8pd$1@dough.gmane.org>

Yury G. Kudryashov wrote:
> 
> 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.

But if it fails you will most likely end up with a stuck server.

Best wishes,
Taco
___________________________________________________________________________________
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:14 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
2010-06-06 11:14           ` Taco Hoekwater [this message]
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=4C0B8301.3020100@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).