access:access_software_testing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:access_software_testing [2010/04/13 21:52] mmatthews |
access:access_software_testing [2012/10/10 17:09] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Access Software Testing ====== | ====== Access Software Testing ====== | ||
| - | The entire AgtekNet software suite is built and tested on a nightly basis. The nightly build and unit tests are run on the development machine //dev.agtek.com// from the //mdm// account. The build is scheduled to run at midnight using cron and executes the script:\\ | + | The entire AgtekNet software suite is built and tested on a nightly basis. The nightly build and unit tests are run on the development machine //dev.agtek.com// from the //mdm// account. The build is scheduled to run at midnight using cron, and executes the script:\\ |
| /home/mdm/build/nightly_build.sh | /home/mdm/build/nightly_build.sh | ||
| Line 12: | Line 12: | ||
| AgtekNet/test/com/agtek/net/storage/server | AgtekNet/test/com/agtek/net/storage/server | ||
| - | The entry point for the tests run by the nightly build is in the java class TestAll. | + | The entry point for the tests run by the nightly build is in the java class TestAll. The unit tests focus on the Access Server and the AccessLib java client side library. The tests run by starting up an instance of the Access Server. The configuration for the server instance is in the file: |
| + | AgtekNet/apps/storage/test.props | ||
access/access_software_testing.1271195547.txt.gz · Last modified: 2012/10/10 17:09 (external edit)
Page Tools
