We are a very small team (1 front-end developer, 1 back-end developer/solution architect, 1 PM/UX) working in Scrum with 2 weeks Sprints.
Up until now, we were mostly working on prototype projects not requiring any testing but one of our MVPs is gaining traction and we've started implementing unit testing as part of our Definition of Done for our user stories.
However, we're now having an issue where testing is taking as much time, if not more, than the development/coding time for two main reasons:
- My devs are not used to the unit testing framework and are still learning.
- There are only two of them, each with their own specialty (front-end and back-end) so they have to do both the coding and the unit testing for their side of the stories.
This has led us to fail sprints because unit testing ends up taking so long that the stories don't get finished before the end of the Sprint. This becomes problematic for medium-sized stories that can't be split into smaller stories because when we add unit-testing estimation, it ends up making these stories so large that a single story ends up taking up almost half of the Sprint capacity.
Would you have any tips on how to improve this process so that testing is more streamlined/faster? Our front-end is using React and currently using JEST for unit testing, and our back-end is built with .NET on AWS but hasn't started implementing unit testing just yet.