Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2009-04-09 | Remove redundant EXTRACT_ONLY and NO_CHECKSUM declarations. | joerg | 1 | -2/+1 | |
Retire NO_PACAKGE as there is no technical reason for it. | |||||
2008-03-04 | Resign from maintaining a lot of packages, so everyone is free to update | rillig | 1 | -2/+2 | |
them at will. | |||||
2007-09-09 | Added a testcase for tar. | rillig | 2 | -3/+27 | |
2006-11-09 | Added a test new case for /bin/sh. | rillig | 2 | -4/+45 | |
2006-09-20 | Added a testsuite for sed(1) to make sure it can handle character | rillig | 2 | -3/+42 | |
classes. | |||||
2006-06-25 | Added a test for the "sort" tool. Fixed pkglint warnings. | rillig | 2 | -6/+47 | |
2006-05-31 | Double the length of the command line argument after each iteration. | rillig | 1 | -1/+2 | |
2005-11-24 | Added more tests for tr(1), including one that feeds 65536 bytes through | rillig | 1 | -1/+20 | |
tr(1). Let's see if there's an implementation with bounded line lengths. | |||||
2005-11-24 | Added testsuite for tr(1). | rillig | 2 | -3/+40 | |
2005-11-24 | Oops. I had put the awk-specific functions into test.subr. Moved back. | rillig | 2 | -19/+27 | |
2005-11-24 | Factored out the generally useable shell functions into tests.subr, as they | rillig | 2 | -31/+36 | |
will be used by almost all test cases. | |||||
2005-11-19 | Don't require too much from a simple awk. 6144 bytes per line must be | rillig | 1 | -3/+6 | |
enough. At least for Solaris. | |||||
2005-11-19 | Print the name of the test case when starting it. This helps in detecting | rillig | 2 | -3/+10 | |
which test case fails. | |||||
2005-11-19 | Make sure that awk can handle strings of length 4096 on the command line | rillig | 1 | -14/+45 | |
and of length 2^20 when copying from stdin to stdout. | |||||
2005-11-19 | Added comments. | rillig | 1 | -1/+4 | |
2005-11-19 | Regression test for the capabilities of the TOOLS. Most of them have | rillig | 3 | -0/+53 | |
many different implementations and are by no way easy to use. This test collects some assumptions about what the tools must be able to handle. It is also meant as a guide on using these tools correctly and reliably. |