Yep, in the last few weeks I’ve committed to develop a few Sharepoint + Infopath based workflows for a client, I’ve been developed sharepoint solutions before, and everytime I touch sharepoint solution code I arrive to the same conclusion:
Sharepoint development is the best example of GDD (Guess Driven Development)
I mean, I know there are just a few ways to do TDD in Sharepoint (using Typemock), but right now develop and test complex sharepoint solutions consist in a few steps:
- Think what you need to do
- Guess how to do it
- Guess what would happen in sharepoint when the solution is deployed
- Build your WSP
- Deploy your WSP
- Run it
- Guess what that “cryptic” error message means…
- Guess your solution to that error
- Repeat until your error message disappears or another one appears.
I think there must be a better way to do it…