User Tools

Site Tools


access:agtek_access_dev

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
access:agtek_access_dev [2018/10/19 19:05]
mjallison created
access:agtek_access_dev [2018/10/19 21:39] (current)
mjallison [Unit Testing]
Line 6: Line 6:
 The chosen IDE is the Intellij community environment,​ although Eclipse may still work. Eclipse ​ The chosen IDE is the Intellij community environment,​ although Eclipse may still work. Eclipse ​
 was the older environment used previously. ​ was the older environment used previously. ​
 +
 +====== Unit Testing ======
 +There are currently 216 JUnit TestCase test functions in the agteknet/​test directory.
 +The best way to test the server is run "​TestAll",​ which runs all the other test suites.
 +JUnit assert failures will be flagged in the IDE.
 +
 +NOTE: The production builds run by Jenkins will fail if any unit test fails. ​
 +
 +It is highly recommended that all new functionality is coded with unit tests
 +(both at the session level and with client api level) to make sure it works
 +reliably before rolling into either limited testing (e.g. key2) or production. ​
 +The unit tests also continue to test for deprecated APIs that may still be utilized ​
 +by older software clients being used by customers.
  
 ====== Packages required by Access ====== ====== Packages required by Access ======
Line 31: Line 44:
   * sl4j-api-1.7.25.jar   * sl4j-api-1.7.25.jar
   * sl4j-jdk14-1.7.25.jar   * sl4j-jdk14-1.7.25.jar
 +  * prooxool-0.9.1jar - Totally deprecated DB pooling (ancient), can probably be removed, but need to change MysqlPool.java
 +  * prooxool-cglibjar - Totally deprecated DB pooling (ancient), can probably be removed, but need to change MysqlPool.java
access/agtek_access_dev.1539975955.txt.gz ยท Last modified: 2018/10/19 19:05 by mjallison