gardener, Interface administrators, Administrators
3,893
edits
Changes
Jump to navigation
Jump to search
m
There is a project working on creating a The test suite for ConTeXt.The homepage is [[https://foundry.supelec.fr/projects/contexttest a set of files that exercise many ConTeXt Test project]]features and are used by Hans for testing releases.
The mailing list can be accessed through the [[https://foundry.supelec.fr/mail/== Where is it?group_id=21 Lists]] section, and in the [[https://foundry.supelec.fr/scm/?group_id=21 SCM]]section you can find the actual test files.
=== Who canThey are on the PRAGMA site [http:/should submit new tests? ===/www.pragma-ade.nl/context/latest/cont-tst.7z here as a 7zip archive].
* Anyone.* But since Hans and Taco are busy enough, users, even beginners, are the ones expected to submit new tests.== How can they be useful? ==
=== Who REALLY should submit new tests? ===On the mailing list, Hans sometimes points one to minimal examples of a feature being asked about. You can recursively grep through the (uncompressed) archive to find the example. For example, I had asked about coupled problems and solutions, for which the relevant mechanism is blocks. To quote Hans: "(there are some examples in the test suite under blocks)." After I unpacked the archive (into <code>/tmp/doc/</code>), the following command located the examples:
=== How to view the existing tests? === In the [[httpsCategory://foundry.supelec.fr/scm/?group_id=21 SCMTools]] you can learn how to connect to the repository through subversion, or you can browse the current repository of tests online. == How can I join in? == === Join the mailing List === In the [[httpsCategory://foundry.supelec.fr/mail/?group_id=21 ListsDevelopment]] section of the server, you will find the contexttest-commits mailing list. The list is not only for commits, it is also the discussion forum of the people working on tests. If you want to do any kind of work for the test project, please subscribe to this list first. === Submit new tests === * create an account on https://foundry.supelec.fr/projects/contexttest* click on <code>[Rrequest to join project]</code>* {{todo|write notes about installing/using svn}} === Any easier way to do that? === * No yet, but it would be nice if a simpler way existed. Perhaps in the future ... === How can I see/compare the results and judge if they're OK? === At the moment, we are still in the collecting phase. There is no point in setting up the testing infractructure until there are at least some tests to be run. What we need right now are simply test files.
no edit summary
== What is it? ==
<pre>$ grep -r -n --include='* If a bug that you encountered gets fixed (on the mainling list).tex' '\<block\>' /tmp/doc//tmp/doc/context/tests/mkiv/blocks/blocks-001.tex:89:\chapter{Normal block use}/tmp/doc/context/tests/mkiv/blocks/blocks-001.tex:91: % test normal block use/tmp/doc/context/tests/mkiv/blocks/blocks-001.tex:164: % test nested block* If /tmp/doc/context/tests/mkiv/blocks/blocks-001.tex:171:\startquestion Is this a question in a new feature is implemented on your requestnested block? \stopquestion/tmp/doc/context/tests/mkiv/blocks/blocks-001.tex:178:Here we call for the nested block:</pre>
