I am currently working on a iOS mobile project for a client which would be considered quite large for a mobile project. The project is made up of two streams iPad and iPhone.
We have 6 developers in total spread across the two applications which effectively do the same thing but have different user experience to differentiate them.
There is a team of testers 5 in total and the project manager. The testers effectively sit there running manual test cases on the application on all the different devices and OS versions we are supporting.
This seems to happen on every single iteration of the project. I guess some observations that I have made is that. To many developers can spoil the broth as you say. Sometimes people don’t ask questions and they reinvent the wheel making the codebase more complicated. Sometimes developers don’t pay enough attention to detail and defects keep going backward and forward as more edge cases come up. More capable developers can be overloaded to fix complicated issues.
The next thing is how do you remove the physical aspect of testing or at least reduce the cost of it on a mobile project.
There are different frameworks like KIF and cucumber which can reduce this but they don’t necessarily stamp out the need for physical testers. Also if you haven’t started with them it can be hard to add them later.
I have been fighting with these in my head for a while. I really want to create a tangible plan for the client going forward which will not only save them money but will improve the process going forward for them and reduce all this time wasted on defects and testing. My first thought is maybe creating smaller scope and as such smaller and more quicker release cycles.
Anyway does anyone have any thoughts out there or ideas? Add a comment if you do.