ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: test suite in the garden
Date: 26 Jul 2005 23:36:38 +0200	[thread overview]
Message-ID: <m2y87t9rmh.fsf@levana.de> (raw)
In-Reply-To: <3140B5FA-6F65-47E1-AAA0-BD8492696241@fiee.net> (Henning Hraban Ramm's message of "Mon, 25 Jul 2005 22:42:28 +0200")


>> It is perhaps a lot of work included, but extending the
>> contextgarden.net in such a way that users could provide test cases
>> which would be typeset with different ConTeXt versions and PNGs
>> compared afterwards ... could make it easier to discover any broken
>> functionality.

It comes down to:

* different context versions needed
* different test documents needed

1) user can select any combination of the above
2) result (one page/png, more pages pdf) can be viewed or downloaded
3) feedback

or perhaps (as I can read between your lines)

a pdf with even number of pages:
left page: original, right page the selcted version. 

So we need test documents and after that context can mix in the pages
from the known good document and the selecte version. 

So you think that users actually download these comparisons?

> Oh, another quest for our magic Patrick! ;-)

Don't call me magic. I am currently trying to understand the tftopl,
pltotf, vftovp and vptovf programs in detail. And I am so miserable at
that; all kinds of optimizations that makes the code unreadable. 

> Let me extend the suggestion, for we miss a ConTeXt test suite for a
> long time now:
>
> - users send test cases
> - test cases get typeset with the actual ConTeXt and converted to PNG
>   (like inline samples)
> - user "votes" if it looks right, if not adds comment
> - test case gets saved, including PNG, ConTeXt version and vote/comments
> - at next update, all test cases get typeset again, and users can
>   "vote" if it looks still ok or at least the same (perhaps it would
>   be  possible to check automatically if the bitmaps are exactly
>   identical)

Again, I doubt that users will actually do these kind of things. I
could provide some interface for documents connected to version
numbers, so you could download a set of .tex files (or one big tex
file) and the related pdf file, but we need to collect good examples.
And I think that testing is very hard: there are so many different
things in ConTeXt that can be tested, so the pdf would result in a few
hundred pages. 

Patrick
-- 
ConTeXt wiki and more: http://contextgarden.net

  parent reply	other threads:[~2005-07-26 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 18:52 Strange behaviour of \bTABLE ... \eTABLE Elena Fraboschi
2005-07-25 20:04 ` Mojca Miklavec
2005-07-25 20:42   ` test suite in the garden (was: Strange behaviour of \bTABLE) Henning Hraban Ramm
2005-07-25 22:12     ` test suite in the garden Hans Hagen
2005-07-26 21:36     ` Patrick Gundlach [this message]
2005-07-26 22:23       ` Mojca Miklavec
2005-07-26 22:38         ` Patrick Gundlach
2005-07-27  7:33       ` Taco Hoekwater
2005-07-25 20:46   ` Strange behaviour of \bTABLE ... \eTABLE Hans Hagen
2005-07-26  8:22     ` Taco Hoekwater
2005-07-25 20:43 ` Hans Hagen

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=m2y87t9rmh.fsf@levana.de \
    --to=patrick@gundla.ch \
    --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).