ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Re: test suite in the garden
Date: Wed, 27 Jul 2005 00:23:37 +0200	[thread overview]
Message-ID: <6faad9f005072615231ef5f138@mail.gmail.com> (raw)
In-Reply-To: <m2y87t9rmh.fsf@levana.de>

Patrick Gundlach wrote:
> 
> >> 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

Once you are done with the fonts ... Different ConTeXt versions also
seem to be useful for all kinds of stuff:
- browsing (& comparing) old source files
- running live.contextgarden.net on older versions (in case the
behaviour in the new version is changed)
- (maybe donloading old ConTeXt versions for whatever reason?)
- modules.pdf
- test suite

> * different test documents needed

This can be done gradually. Of course, it is impossible to have a very
good test suite, but at least some features can be tested; broken
functionality would be noted much later otherwise (if ever). If you
let the users add stuff, the suit will gradually grow. It would be
much easier then to say "take a look: my document is OK with the
version this-and-that, but since the version this-and-that something
strange happens" when reporting a bug.

(Perhaps testing documents should also have at least some very basic
set of labels: very important to test, interesting test case, just
temporary or one-time testing. Or at least some switch to leave the
document there, but to remove it from the list of "test suite" when
next ConTeXt version is out. 100 versions and 1000 documents ... can
slow down your computer a bit.)

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

Converting multiple-page pdf to png-s should also be possible. Take
http://archive.contextgarden.net/thread/20050701.172657.13cd3fb5.html
for example (the difference seen on the third page). But the number of
pages or at least the number of document with a big number of pages
has to be limited somehow.

> 3) feedback

Perhaps some labeling in case the results differ?
- Label A: to inspect what's going wrong
- Label B: it's ok, it's only a new feature, not supported before
- Label C: ok, the bug was removed (some page inbetween differ)
- Label D: ...

Only the label A and perhaps some others would be interesting then ...

> 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?

The most important would be some graphical representation (different
colors if a document doesn't compile or if it changes), but allowing
the user to download a selected document compiled with a selected
version should be possible.

> 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.

No, this wouldn't make any sense. I was thinking about PDF to PNG
conversion and bitwise comparison of the files, which could be made
automatically. Each time a new version would be uploaded, the
documents would be compiled, any compilation errors caught and any
image differences reported. Only if any of those two cases would be
reported, the results would be inspected manually.

Sorry Patrick :),
    Mojca

  reply	other threads:[~2005-07-26 22:23 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
2005-07-26 22:23       ` Mojca Miklavec [this message]
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=6faad9f005072615231ef5f138@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.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).