Testing during re-factoring
Hi folks - I'm brand new to this site and I have a question about testing during re-factoring. My SCRUM team is going through a period of at least 6 three week iterations of re-factoring. As a tester, I am finding it hard to stay engaged. I am wondering how other teams handle the testing aspect of re-factor iterations.
I'm sure re-factoring in itself doesn't effect engagement. What is the core issue?
Lack of new features to test, so everything is heavy regression?
Lack of things to do (if everything is automated)?
Lack of features to test, no user stories directed to the user and their interaction with the software. Yes - heavy regression; mostly manual - the reason for not feeling engaged. Repetitive tasks over and over - a perfect recipe for feeling disengaged. In addition to that, it's a constant game of "I just re-factored x, but it is not ready to regress test because y will be re-factored next, and that will affect x."
Originally Posted by dlai
Use the time to automate the regression.
I think we all have to find what it is that excites us to stay engaged. The QA profession is a pretty daunting area. Even as an SDET,that specializes in large scale test automation and CI systems, I do feel like I don't get the respect form other developers even though I'm writing much more complicated multi-threaded distributed code than they are.
For me, I see my role as a learner. Since I am not pigeonholed hole into any one component or tier, I see the goods and bads of the system as a whole, and how the engineering process contributes to that. So what keeps me excited is known that every little thing I learn I feel is applicable in being a good CTO in a company I will one day start.