Differences

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

--- access:agtek_access_dev [2018/10/19 19:18]
mjallison [Packages required by Access]
+++ 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
 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 ======

AGTEK R & D Wiki