Test Procedure

Overview

Testing SeaBreeze is not entirely trivial. The driver supports at least a dozen different spectrometers models, some of which are End-of-Life and no longer readily obtainable, and many of which are prohibitively expensive to acquire simply for test verification.

Combined with the two different APIs (SeaBreezeWrapper vs SeaBreezeAPI), at least 8 popular architectures (WinXP, Win7-32, Win7-64, Win8-32, Win8-64, Linux-32, Linux-64, MacOS) and the number of client languages (C, C++, C#), and prospects for comprehensive testing may seem remote.

Ocean Optics is in the process of provisioning a regression test box, which would be configured with a continuously-available set of common spectrometers (STS, USB2000+, QEPro, Ventana, NIRQuest etc). Once that is in place, we will configure nightly automated tests against a broad selection of typical customer environments, which would include checking out the latest code from /trunk, building it on common compilers, and running the existing tests under SeaBreeze/test.

Until that time, we ask that developers test all changes against at least one supported spectrometer, on one OS from one language. Please include a summary of your test environment in Code Review requests, so that reviewers may test your branch against different hardware so as to provide further verification.