If i was with an LA i would probably insist they tested it on my data. In the end it's going to save them hassle supporting me later
less calls from me = happier supportline monkey
Last edited by Sivadam; 29th November 2011 at 10:46 AM.
Just thinking out loud fellas, that's all.
I would imagine a centrally hosted test facility. It doesn't take that long to restore and upgrade a set of data. I wouldn't say do all of them. But every little helps.
If you look at the last couple of issues, they might have been caught if the testing net was cast a little wider. Homepage panels broken, pastoral structure glitch, ...
I'm not having a go at LAs or trying to throw more work your way, you guys do a sterling job, just wondering if as a community there are better ways to help ourselves. UAT isn't necessarily the answer and not convenient for all! Saying Capita should do more vigorous testing, also isn't helping either though. It's the data that does the testing, not a person or establishment.
As I said earlier, if I had UATd this release (I actually attended UAT for SLG, to get a heads up on the the Homework Webpart!), then I would have noticed no problem whatsoever. I even ran a Spring Census Test after we upgraded to 7.142 before I knew that Fileset90 had been omitted!
Last edited by Sivadam; 29th November 2011 at 12:08 PM.
It's real needle in haystack stuff. The fact it is taking all this time to fix proves it is not as simple as we would like to think it is.
My pastoral structure seems fine, and i've doctored it to create an admin tier, so even admin staff can be assigned a division to be reported on .
Just glad my LA did not approve my Census in time............always seem to wait a couple of months these days after being stung for too many years applying the new releases as soon as they become available.
I'm sure from the testing that is done, loads of these issues come about and are fixed before we even notice, and there is not such a big deal made. If the needle is in a pile of 22,000 pieces of straw, the more we lift the more chance we have of finding any flaws.
We don't necessarily need in depth testing just more varied testers. If the issue is buried deep in some obscure part of curriculum planner when accessed by a head of department, we will miss it, but if its a case of look at your pastoral structure, then we can all do that. As well as, try taking a register, run a report, enter data in a marksheet etc.
I don't test sims that well, but if it's an FMS upgrade, i make them do lots of different tasks to make sure it is all going to work. Our fees are processed from sims into FMS and our payroll comes out. We don't want more than a months delay! And often, an upgrade might happen mid-month - v.scary. Even a month, when i only get around 8 days contact time, isn't a great deal to solve a big problem.
We have about 150 schools. If the failure on this was 3/1000 the odds are, none of our schools would be affected. I'm afraid we got caught too may times that we are not allowed to roll out, neither are we allowed to test. Perhaps if the schools paid more, we could employ someone to test more....
Update from SupportNet:-
*** SIMS 2011 Autumn Release - Please Read 29/11/2011
We are in the final stages of investigating the issues with the autumn release. Unfortunately it has proved more complex to fully investigate than we had anticipated.
I will provide an update with more details by COB tomorrow at the latest.
There are currently 1 users browsing this thread. (0 members and 1 guests)