What does everyone do for testing after a Lithium release? So far we've just been keeping an eye out, but have not instituted a testing protocol. But we'd like to be sure that the custom functionality we've built continues to work with each release.
Has anyone had anything break after a Lithium release, and do you think this is a concern? Any best practices and thoughts are much appreciated!
Hey iftomkins
I manage our Lithium deployments in a similar way to that of the help site I manage. Obviously there is UAT/SIT testing in our stage prior to the deployment however i also have a series of post release test scripts which i or my team run.
Typically these will test the core functions within the community or the bits we know could be broken easily, especially anything that is a customisation. I have only really done one major release in the community however prior and after the release i did let the community know what we where doing and asked our super users to keep us posted on any fallout of issues found.
So far this has proved very helpful.
Hi Stephen, great advice, though I realize I didn't express my question clearly.
The Lithium releases I am asking about are releases made my Lithium itself, such the recent 14.2 and 14.3 versions, which include new features and upgrades. Have you ever heard of anyone experiencing an issue/conflict when such a release is deployed?
I get ya...
I have not noticed any issues with my own community but i have seen "not often" some ppl report small bugs following a release but you will typically get the release in your stage a few weeks or at least a week prior to going into production so you can test in stage and if you did notice an issue you could get support to delay your deployment to production whilst you work on a fix/find root cause.
Hope that helps.
