| 2 | | |
| 3 | | == The testsuite in modern versions of nss == |
| 4 | | |
| 5 | | The current testsuite is designed to catch regressions in new additions, |
| 6 | | so every new addition should come with one or more tests (I noticed from |
| 7 | | the diff between 3.40 and 3.40.1 that there ''were'' tests, although the |
| 8 | | book said there was not a testsuite). |
| 9 | | |
| 10 | | Unfortunately, it needs to be run with nspr and nss directories side by |
| 11 | | side in the top-level directory (which is how combined nspr+nss tarballs |
| 12 | | present things), and built unoptimized (BUILD_OPT=0). |
| 13 | | |
| 14 | | For further details, see [https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Sources_Building_Testing] |
| 15 | | |
| 16 | | I managed to get that process working on nss-3.40-with-nspr-4.20 but not with 3.40.1. |
| 17 | | {{{ |
| 18 | | make -C nss nss_build_all USE64=1 |
| 19 | | }}} |
| 20 | | That took almost 25 minutes, I don't think the particular CPU makes a lot of difference. |
| 21 | | For that run, 6 tests failed (look for ' FAILED' in the output), all reporting that a |
| 22 | | peer's certificate has expired. |
| 23 | | |
| 24 | | Unless you intend to hack on nss/nspr, running the tests on a released version is not recommended. |
