Commons Testing Organization ============================ Commons testing can be broken into these basic categories: 1. unit - which really means "anything not fully integrated" 2. functional - which run against a fully integrated system, but configured for testing 3. performance - these run against a fully integrated system, configured for potential production style deployments ## Unit Tests ## Functional Tests ## Performance Tests
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 9249 | tjuricek |
Added test p4d setup, and reorganized some core code. I've decided to not use InterfaceBuilder in this project, because I don't like that the .xib files are not very easy to merge, and the object lifetimes are a bit more difficult to trace. The DocHubController will operate as the app delegate, and will create views manually. Using the gradle toolchain to setup p4d. To use, execute: ./gradlew startPerforce ./gradlew initPerforce # only needed the first time This creates the p4d that uses build/perforce/work |