Difference between revisions of "Test suite"

From ConTeXt wiki
m (moved Test to Test suite: More descriptive name)
(fix the links)
Line 2: Line 2:
  
 
There is a project working on creating a test suite for ConTeXt.
 
There is a project working on creating a test suite for ConTeXt.
The homepage is [[http://foundry.supelec.fr/gf/project/contexttest/ ConTeXt Test project]].
+
The homepage is [[https://foundry.supelec.fr/projects/contexttest ConTeXt Test project]].
  
The mailing list can be accessed through the [[http://foundry.supelec.fr/gf/project/contexttest/mailman/ Lists]] section, and in the  [[http://foundry.supelec.fr/gf/project/contexttest/scmsvn/ SCM]]
+
The mailing list can be accessed through the [[https://foundry.supelec.fr/mail/?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.  
 
section you can find the actual test files.  
  
Line 19: Line 19:
 
=== How to view the existing tests? ===
 
=== How to view the existing tests? ===
  
In the [[http://foundry.supelec.fr/gf/project/contexttest/scmsvn/?action=AccessInfo SCM]] you can learn how to connect to the repository through subversion, or you can browse the current repository of tests online.
+
In the [[https://foundry.supelec.fr/scm/?group_id=21 SCM]] 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? ==
 
== How can I join in? ==
Line 25: Line 25:
 
=== Join the mailing List ===
 
=== Join the mailing List ===
  
In the [[http://foundry.supelec.fr/gf/project/contexttest/mailman/ Lists]] 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.
+
In the [[https://foundry.supelec.fr/mail/?group_id=21 Lists]] 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 ===
 
=== Submit new tests ===
  
* create an account on http://foundry.supelec.fr/gf/project/contexttest/
+
* create an account on https://foundry.supelec.fr/projects/contexttest
 
* click on <code>[Rrequest to join project]</code>
 
* click on <code>[Rrequest to join project]</code>
 
* {{todo|write notes about installing/using svn}}
 
* {{todo|write notes about installing/using svn}}

Revision as of 14:16, 16 December 2015

What is it?

There is a project working on creating a test suite for ConTeXt. The homepage is [ConTeXt Test project].

The mailing list can be accessed through the [Lists] section, and in the [SCM] section you can find the actual test files.

Who can/should submit new tests?

  • Anyone.
  • But since Hans and Taco are busy enough, users, even beginners, are the ones expected to submit new tests.

Who REALLY should submit new tests?

  • If a bug that you encountered gets fixed (on the mainling list).
  • If a new feature is implemented on your request.

How to view the existing tests?

In the [SCM] 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 [Lists] 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


TODO: write notes about installing/using svn (See: To-Do List)


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.