Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

iSQI Exam CTFL-AT Topic 3 Question 40 Discussion

Actual exam question for iSQI's CTFL-AT exam
Question #: 40
Topic #: 3
[All CTFL-AT Questions]

Why is regression of software a high risk in agile projects?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Gabriele at Sep 16, 2024, 11:59 AM

Limited Time Offer

25%

Off

Get Premium CTFL-AT Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Gabriele
3 months ago
I'm surprised option A is even an option. Test-driven development is all about ensuring existing functionality remains intact!
upvoted 0 times
Laurel
1 months ago
D) There is code churn due to change in business needs over several sprints.
upvoted 0 times
...
Merissa
1 months ago
B) Test automation can cause regression of software in the test environment.
upvoted 0 times
...
Rosendo
2 months ago
A) Test-driven development means that existing functionality is not considered.
upvoted 0 times
...
...
Pilar
3 months ago
D is definitely the way to go. Agile's focus on responding to change means the codebase is in a constant state of flux, making regression a major concern.
upvoted 0 times
Elvera
2 months ago
That's true, test automation can sometimes introduce unexpected issues when changes are made to the codebase.
upvoted 0 times
...
Bonita
2 months ago
Test automation can cause regression of software in the test environment.
upvoted 0 times
...
Isabella
2 months ago
D is definitely the way to go. Agile's focus on responding to change means the codebase is in a constant state of flux, making regression a major concern.
upvoted 0 times
...
...
Barbra
3 months ago
Haha, option C is a good one! Regression is a 'feature', not a bug. We should just embrace the unexpected failures, right?
upvoted 0 times
Malcom
2 months ago
User 3: But what about the code churn due to change in business needs over several sprints?
upvoted 0 times
...
Raina
2 months ago
User 2: Raina is right, we should just embrace the unexpected failures.
upvoted 0 times
...
Barney
3 months ago
User 1: Haha, option C is a good one! Regression is a 'feature', not a bug.
upvoted 0 times
...
...
Brigette
3 months ago
I think B is the correct answer. AuBrigetteated tests can sometimes introduce new issues or fail to catch regressions, increasing the risk of software regression.
upvoted 0 times
...
Lorean
4 months ago
Option D seems like the most reasonable answer. The constant change in business needs during sprints can lead to significant code churn, making regression a high risk in agile projects.
upvoted 0 times
Keshia
2 months ago
That's true, test-driven development may not cover all existing functionality.
upvoted 0 times
...
Lezlie
2 months ago
Test automation can also play a role in causing regression of software.
upvoted 0 times
...
Elliott
2 months ago
Yes, the constant change in business needs can definitely lead to code churn.
upvoted 0 times
...
Shalon
3 months ago
Option D seems like the most reasonable answer.
upvoted 0 times
...
...
Gianna
4 months ago
I believe regression is built into software as a safeguard against unexpected failures, but it can still be a high risk in agile projects due to the constant changes.
upvoted 0 times
...
Horace
4 months ago
I agree with Margery. Test automation can also cause regression of software in the test environment, making it a high risk.
upvoted 0 times
...
Margery
4 months ago
I think regression of software is a high risk in agile projects because of code churn due to change in business needs over several sprints.
upvoted 0 times
...

Save Cancel