Page 1 of 1
Code testing and implementation
Posted: Tue Sep 11, 2012 8:33 am
by rbwheeler
It is evident from the numbers of bugs that keep showing up on this site as well as others that perhaps there is a problem with automatic code testing and/or consistent methodology.
Posted: Wed Sep 12, 2012 8:44 am
by lisaan
If you're interesting in testing the Calendar application you can start by going to the SWARM page for Calendar. Go to
https://tech.lds.org/projects and select Calendar. Once it's on your list, click on the link and you'll see all the options there including SWARM. Thanks.
Posted: Sun Sep 16, 2012 4:15 pm
by rbwheeler
Seems like too many problems are showing up when the application is exposed to the user. Could this be a code debt problem or lack of complete automatic testing and/or acceptance testing?
Posted: Wed Sep 19, 2012 11:58 am
by lajackson
Unless I misunderstand, you seem to have asked the same question twice. The Calendar undergoes significant testing before it is released. Many at this Forum have been involved. You are welcome (and have been invited) to participate in that testing.
You are also welcome to identify and report specific bugs you find with enough detail that developers are able to duplicate them and prioritize them for resolution. In my experience, no matter how thoroughly code is tested before it is exposed to the user, the user will find something that has not been anticipated.
Even among those of us who use the Calendar in production, we continue to find scheduling scenarios that never were considered by any of us. Testing in Beta finds many of them. Swarm testing finds even more. And the user probably still has not found all of them.
But if the developers waited until all the problems were identified before release, we would not yet even have a calendar.