ESS_GUIESS_GUI_DocsESS_GUI_batch_fittingESS_GUI_bumps_abstractionESS_GUI_iss1116ESS_GUI_iss879ESS_GUI_iss959ESS_GUI_openclESS_GUI_orderingESS_GUI_sync_sascalccostrafo411magnetic_scattrelease-4.1.1release-4.1.2release-4.2.2ticket-1009ticket-1094-headlessticket-1242-2d-resolutionticket-1243ticket-1249ticket885unittest-saveload
|
Last change
on this file since 20f07dbc was
35ec279,
checked in by krzywon, 10 years ago
|
|
Completed the SANS to SAS conversion on the tests. src.sas is left.
|
-
Property mode set to
100644
|
|
File size:
852 bytes
|
| Line | |
|---|
| 1 | Running Tests |
|---|
| 2 | ============= |
|---|
| 3 | |
|---|
| 4 | Tests are stored in subdirectories of the test directory, as |
|---|
| 5 | *package/test/utest_\*.py*. Other files in the test subdirectory are |
|---|
| 6 | data, expected output and other support files. Before running any tests |
|---|
| 7 | you must first run *setup.py build* in the root. Tests are run against the |
|---|
| 8 | current source directory with run magic to find the compiled code, so you |
|---|
| 9 | only need to rebuild between tests if you are modifying the C code. |
|---|
| 10 | |
|---|
| 11 | Tests can be run in Eclipse (or other IDE) by selecting *utest_sasview.py* |
|---|
| 12 | and selecting run. This will run all of the tests. To run tests for one |
|---|
| 13 | one package, edit the *utest_sasview.py* run command and add the package |
|---|
| 14 | directory to the command arguments. To run an individual test, |
|---|
| 15 | select *run_one.py* and edit the command arguments to include the path to |
|---|
| 16 | the desired test file. |
|---|
Note: See
TracBrowser
for help on using the repository browser.
