Hi ya'll -
Wondering if any of you have a standard set of regression tests you run when your community staging site is upgraded. If so, it would be amazing if you'd share your tests!
I generally poke around somewhat haphazardly and test / document the new features, but this isn't always adequate. For example, today when writing up documentation on the new-to-us-in-19.6 "category subscription" feature, I stumbled across the fact that our hamburger menu is blank across our entire community. This would have been rather embarrassing to release into the wild.
In summary... any sample tests or best-practices around handling Khoros Community releases would be most appreciated!
I have heard from our TAM that the blank menu issue only affects staging instances, not prod. We are going to hope that is indeed the case and move to 19.7.
Interesting, and not sure that's accurate. I know of another community that's experiencing this issue on production.
@CarolineS Our staging env was upgraded to 19.7 and I now see the items in the hamburger nav menu, but they're out of order. Are you seeing the same (if you've received 19.7)?
@StephenB - we did indeed get 19.7 on our staging site, but our hamburger menu is still blank. I had heard about this out-of-order issue from our TAM though - so it's a known issue on the Khoros side.
We wrote some automated tests for the most important usecases such as register a new user, login/logout, post, navigate etc. to make sure that all basic functionalities are working. We run these on stage prior to every release. We do that also for most of the common browsers. With new (custom features) we continuously adopt or extend those tests.
Being a one person team, I didn't test anything in stage and now I have a reordered hamburger menu on production.
Luckily, I have a private community where most people 'land' in the section they want from links in our products. Otherwise this 3 week error, would be a big issue.
I will be trying to adopt @MrB77 testing.
Hi @mhock they are client specific but could be adopted. The thing is that we do this for our customers so I can't share them but I'm happy to share some of the insights so you would be able to replicate this. There would also be an option that we build those test cases for you. Feel free to ping me if you would like to further exchange.