Continuous integration is great, but it's not a magical solution. B is the way to go - too many builds can definitely compromise testing. Gotta keep that quality up, folks!
A is an interesting one. I can see how teams might over-rely on unit tests and forget about the bigger picture. But I think B is the best answer here. Quality testing is key, and too many builds can really impact that.
Haha, D definitely sounds like something my manager would say. 'Developer's workload is increased, which can result in a reduction of output.' That's a risk alright, but not one that continuous integration itself introduces.
I'm going with C. Teams no longer have the ability to run manual tests, as all tests must be automated. That's a real risk of continuous integration that I've seen in my experience.
I think the correct answer is B. Testers sometimes have too many builds to test, which reduces the quality of testing. Continuous integration can definitely lead to an increased workload for testers.
Jolene
29 days agoWilliam
1 months agoMy
1 months agoCharisse
2 months agoGayla
23 days agoJunita
1 months agoViola
2 months agoLuis
2 months agoCurtis
2 months agoChaya
2 months ago