Open Bug 843369 Opened 12 years ago Updated 2 years ago

Change NSS tests so they can be run on production test slaves

Categories

(NSS :: Test, enhancement, P5)

enhancement

Tracking

(Not tracked)

People

(Reporter: coop, Unassigned)

References

Details

Our first pass for bug 648676 will likely involve running existing NSS tests on the build slave after the build has been compiled and uploaded. At some point in the future, we would like to run the NSS tests on the test slaves rather than on the build slaves. This will give us testing on a wider array of target operating systems.
kaie and rrelyea already have done most (if not all) of the work here, because we needed it for the current Android test automation. Also, I think Elio may have some experience with running the tests in this way. In particular, look at the target package_for_testing in: https://mxr.mozilla.org/security/source/security/nss/tests/remote/Makefile#68 That target will build a tarball that contains the build outputs and the test scripts and other test inputs. If you extract that archive, then you can run the runtests.sh script which will run all the tests, properly configured.
Severity: normal → S3
Severity: S3 → N/A
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.