-
Notifications
You must be signed in to change notification settings - Fork 13
Testing
This page captures the various forms of testing used to exercise the NGDS.
Unit tests exercise methods in the code base. These tests are automatically run by the continuous integration system and the results are posted. Build results are available at http //node.usgin.org:8088/job/ext-ngds/.
Clicking on this link gives a "Connection Refused" error from Princeton. rwschwanke This was a local link and is not valid. When (if) continuous integration system is re implemented, results should be available at a public URL with updates on the GitHUB repository landing page. smrazgs
Component- and integration-level tests exercise the server-side code. These are executed by simulating the front-end via HTTP calls and testing assertions against the back-end to determine whether the test has passed or failed. As these tests are being authored we are exploring ways to integrate their execution and integrate them into the continuous integration system. If they cannot be integrated we hope at least to have a way to automate the execution of the tests (i.e. a script that will run them all and report the results.)
Currently, client testing exercises both the client-side logic and the application as a whole. It is performed by a combination of automated and manually-executed tests. The results are documented on the NGDS Manual Testing Results page. Manual tests follow manual test scripts collected in the Manual Test Scripts Home page. Automated Testing UI with Selenium will be run frequently during and at the end of each sprint.
These are tests that minimally demonstrate that a previously working functionality is still working. The regression tests are generally sorted most-recently-fixed first. Each test is marked with one or more issue numbers that it supposedly tests for.
These tests are listed in a compact tabular form in Query Regression Tests. In most cases, they should work equally well on Map and Library page, except that some query results will not render on the Map.
These tests are spelled out as user actions in Non-Query Regression Tests.