The second round of testing went well. Tonight's setup: *Test Server: *Ubuntu 12.04 running on VirtualBox 4.1.16 (Windows 7 Host) *Java:* java version "1.6.0_32" Java(TM) SE Runtime Environment (build 1.6.0_32-b05) Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode) *Tomcat:* 7.0.27 from Apache distro with self-signed certificate, trusted by JVM default startup settings (i.e. started up with bin/startup.sh, no special memory configuration) *MySQL: *5.5.22-0ubuntu1
Builds succeeded with the Ubuntu stock OpenJDK as well (OpenJDK Runtime Environment (IcedTea6 1.11.1) (6b24-1.11.1-4ubuntu3), OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)), but all of my testing was done with the Oracle JDK. Tonight I checked out the JPA ticket registry, JPA service registry, and JDBC audit trail. Everything worked as expected except for a ClassCastException I found in the JpaTicketRegistry when the new ServiceMonitor tries to access its stats. (Filed as CAS-1135<https://issues.jasig.org/browse/CAS-1135> .) I specifically tried to test the issue of not being able to update the JPA service registry while the JDBC audit trail manager is enabled, and it seemed to work in 3.5RC2. However, I couldn't get it to fail in 3.4.12, so take that with a grain of salt. (In other words, I was able to successfully update the JPA service registry with the JDBC audit trail manager sharing the same data source and transaction manager.) I'm not sure what the setup is that will make it fail, but it doesn't look like it's an issue with MySQL. (MySQL, of course, is laden with its own issues in general, but I won't get into that now. :) ) Aside from those two issues, though, everything that I hit tonight seemed to work as expected. I only tested a small fraction of the entire application, but hopefully the parts I did manage to QA will prove useful. If anyone has any questions, please let me know. Good night! - Drew On Thu, Jun 7, 2012 at 4:30 PM, Drew Mazurek <dmazu...@unicon.net> wrote: > Hey folks... last night I did some CAS 3.5.0 RC2 QA and wanted to post the > results. So far, I just went through a build, install, and some basic > functionality testing. I started setting up MySQL to do some more advanced > testing, but it was getting pretty late, so I'll do some more testing > tonight. Everything looks great so far: > > *Test Server: *Mac OSX 10.6.8 > *Java:* > Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-10M3635) > Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode) > *Tomcat:* 7.0.27 from Apache distro > with self-signed certificate, trusted by JVM > default startup settings (i.e. started up with bin/startup.sh, no > special memory configuration) > > Tests: > > mvn clean install: pass, no issues > > Basic ticket issue and validation, protocol: > > CAS 1.0: (tested via manual ticket issuance and validation with browser > and wget): > > - pass validate success > - pass validate failure > - proper message formatting for both (with proper line endings) > - renew=true on validate with presentation of primary credentials: > pass (result: yes\nnetid\n) > - renew=true on validate with single sign-on: pass (result: no\n\n) > > > CAS 2.0: (tested via manual ticket issuance, wget, and Java CAS client > v3.2.1): > > - pass serviceValidate success > - pass serviceValidate failure (text response doesn't exactly match > spec -- extra ' (single quote) around wording, no issue) > - pass proxyValidate success, no PT > - pass proxyValdiate failure, no PT > - pass proxy ticket issuance > - pass proxyValidate success, with PT > - pass proxyValidate failure, no PT > - pass renew=true on validate, primary credentials presented > - pass renew=true on validate, SSO credentials (result = invalid auth; > test passed*) > - pass gateway=true > > * This test passed through manual ticket validation with wget. However, > the CAS client behavior I experienced made it seem the CAS Java filter > (v3.2.1) wasn't sending renew=true on ticket validation even though the > servlet init parameter was being set. Not 100% sure of this, but if I have > the time, I'll take a closer look tonight. > > Service Registry: > > - pass included services, in-memory registry > - pass excluded services, in-memory registry > - pass updating service list through service manager > - more testing tonight for database-backed service registry > > Statistics & Ticket Expiration Policies > > - pass ST expiration > - pass TGT expiration > - pass ticket usage count (e.g. 1 for service tickets) > - results displayed properly on statistics page > > Health Monitor > > - pass very basic check > > > That was it for the nitty-gritty protocol stuff. Tonight I'm hoping to > get to some of the more interesting tests. Stay tuned... > > - Drew > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
