 Hi everyone, yes my name's Margaret but please call me Meg, everybody else does, I think it's only my mum who still calls me Margaret. So I'd like to talk to you today about my experiences with testing for the upgrade process. I'd like to also establish I am not a developer. There's a couple of my development team in the room, I never understand a word they say. So I work for Catalyst, I work for the Australian team and as part of that team I'm an LMS consultant and we've worked, I've worked with universities, charities, government, retail, business pretty much the whole range. We've started in 1997 in New Zealand and have spread since worldwide so if you want to find out about any of our services please come and see us and also if you missed the lifesaver kit yesterday come and grab one we made some more up. Catalyst is a fun team, I really love working with these guys, again the guys in the room today have always answered my questions and I just so prepared to go above and beyond for our clients. We also do have a food obsession, particularly pizza. I'm an ex-high school teacher, I've been working with Moodle for over 10 years now, I think I started with 1.9, I've worked in different industries as well as with partners. I grew up in Newcastle Australia, which is a beach town now living in Sydney and range of different hobbies that I've listed there. The photo here today is of me with my mum. Now there's a reason I've chosen this photo if she finds out I'm in deep trouble. I consider my mother a saint now I know a lot of you will say the same thing but the reason my mother is a saint is quite simple. I'm the ninth of 10 children. She has done an amazing job with us and the reason I'm telling you about this is because as a parent she had to learn that she can't do the same thing with each of her 10 children. We are all very different from each other. She's had to learn to adapt and customize her parenting process. To give you an example, I was daddy's girl growing up. If there was a tree to climb then I was generally up at. I never ever had a Barbie doll. I had absolutely no interest in it. So at four years old my mother takes me to a vaccine clinic not unlike the ones we've seen over the last couple of years and we join the queue for the vaccines one gets at the age of four and the pretty little girl in front of me is crying and crying and my mother knowing my preference looks at me and goes you're gonna do that? Nope. Here's my arm. Still have no problem with needles to this day. So when we're talking about customizing your testing process and as much as Davo and the work he does with automated testing is fantastic we still need that human testing element. And when you go to upgrade the best time to start planning that testing process is at the very start when you are preparing for the upgrade itself. So why do we test? At Catalyst we've come across various issues that come up as a result of the testing process that we find with the testing process. It gets rushed, it gets glossed over, we're tired. This upgrade process could have taken us a lot of time and we just want the damn thing done. Simple things get missed, we often don't discover issues till after go live, let's be honest, students are the best testers. And consideration is often not given to our customizations and integrations. So when do you start planning? At the start. We can also learn a lot of information for the upgrade process as well when we start looking at how we're going to go about testing. So this means that we can make sure we cover everything and get through that process as best we can. I need to know how my site is used. What plugins do I have? What activities is used? What's not used, etc. So to give you an example, here's a plug-ins overview page. Always look at your plug-ins overview page for those additional plug-ins. Because what you might notice here is the dialogue plug-in. That first four digits of that number tells me this was done in 2017. Alert, alert, it's old. I need to stray the way to go. Hey Pete, down the back. Can you double check that plug-in and see whether we can upgrade it as part of the process? I haven't got to testing yet, but I've learned something that's going to help Peter with his process. The activities use page is another really good one to look at when you're planning that testing. Why? What's used lots, what's not used at all? And even little things like, we only have three instances of workshop. I think workshops are a great tool, no one uses it. But maybe I can find out there's a champion for the workshop activity in my organization and they can help other people learn how to use it. You'll also notice something very interesting about the dialogue. It's not being used. So now I can say to Pete, Pete, get rid of the dialogue plug-in please for this upgrade. The other thing is, how is my site being used? It's unusual. This is the permissions page for a single activity, for a single assignment that I helped create with a client who had a very unusual situation where he needed his non-editing teachers to upload documentation into the course space. But students can't access it, students can't see it, etc. So we just played with the permissions so that students have no permission now in that activity and the non-editing teacher gets to submit. It's an unusual usage, need to make sure I test that as well because it's out of normal scope. And of course, the other things to remember, we need to look at our roles. Have we customised a role in any way? Have we created a custom role? What are our integrations? Do we need to go and look at our user tours again? Do our user tours test our user tours? Browser compatibility? Have you checked with Firefox? Have you checked with Chrome? Have you checked with that thing called IE? And also device, tablet, phone, etc. And go and test your new features. I do look at the new features page with all the tracker items. I do have a quick look at it. The bits that make sense to me, I go and read. The rest of them I don't. But also the new features page will give you things, go and have a look at them, go and test. And consider your roles. I actually had a client once who used to hire a student to test the site as a student. Make sure you've looked at all your notes, you've included everything. Develop that checklist to go through, be detailed with it and have more than one person on your team. You cannot be the only person testing. Once you've finished, make sure you give your results a good review, have a look through them, discuss them, get everybody involved with it. What might cause the issues for your users? What are they going to complain about the most? And therefore do my plans for upgrade need to change? Should I have the downtime for that upgrade? Longer, so we've got a lot of time to test. So start planning, review your usage, be aware of your new features, remember your roles, test your integrations carefully, have a detailed checklist, have a team and review your results carefully. Thank you very much.