Other than testing everything possible in the enti...
# cfml-general
d
Other than testing everything possible in the entire app, any thoughts on what to test after a java update, beyond "did the server start up ok"? One piece we've had break is PDF generation. Any other ideas?
j
I would suggest testing how the dates work after that one jvm argument required to deal with how D vs d worked in dateformat - https://www.carehart.org/blog/2020/11/24/breaking_change_in_cf2021_dateformat_D_vs_d
d
@Jim Frankowski Thanks, good idea. We're only coming from jdk-11.0.18, and pretty recently before that jdk-11.0.17, so we already had that jvm arg in place. Keep em coming folks 🙂 What else have you seen get broken by java updates?
j
one more thing - make sure your keystore gets updated...
e
automate your testing. Plenty of ways to do this. One of the most "Basic" ways is to install autoIt on a machine, run through the tests in record mode, then play the "recorded" macro back
m
Check any cfhttp calls, they are changing defaults and supported algorithms and TLS defaults.