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 CTFL-AT Exam - Topic 3 Question 40 Discussion

Why is regression of software a high risk in agile projects?
B) Test automation can cause regression of software in the test environment.
A) Test-driven development means that existing functionality is not considered.
C) Regression is built into software as a safeguard against unexpected failures.
D) There is code churn due to change in business needs over several sprints.

iSQI CTFL-AT Exam - 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:

0/2000 characters
Submit Cancel
Charlena
9 months ago
Test automation can definitely introduce new issues if not managed well.
upvoted 0 times
...
Lenna
9 months ago
Yeah, business changes lead to a lot of unnecessary bugs.
upvoted 0 times
...
Jodi
9 months ago
Surprised to see regression as a safeguard, that doesn't sound right!
upvoted 0 times
...
Hermila
10 months ago
I think test-driven development actually helps prevent regression.
upvoted 0 times
...
Theola
10 months ago
Code churn is a big issue in agile, totally agree!
upvoted 0 times
...
Ryan
10 months ago
I think test-driven development is supposed to help, but I wonder if it really prevents regression or just shifts the focus away from existing features.
upvoted 0 times
...
Alita
10 months ago
I feel like regression is a big concern because of all the changes in requirements during sprints, but I can't recall the exact reasons why.
upvoted 0 times
...
Yoko
10 months ago
I’m not sure if test automation itself causes regression, but I think it can lead to missed bugs if not done carefully.
upvoted 0 times
...
James
11 months ago
I remember discussing how code churn can really impact stability in agile projects, especially with frequent changes.
upvoted 0 times
...
Quentin
11 months ago
I'm pretty confident about this one. Agile projects move quickly, with frequent iterations and changes. This means there's a higher risk of regression, where new features or bug fixes accidentally break existing functionality. The key is to have a strong focus on test-driven development and continuous integration to catch these issues early.
upvoted 0 times
...
Sherell
11 months ago
Okay, I think I've got this. In agile projects, there's a lot of code churn due to changing business needs over multiple sprints. This can lead to regression issues, where new changes inadvertently break existing functionality. The key is to have a robust test automation suite to catch these regressions early.
upvoted 0 times
...
Jettie
11 months ago
Hmm, I'm a bit confused by this question. I know regression testing is important, but I'm not sure why it would be considered a high risk in agile projects specifically. Maybe it has something to do with the frequent iterations and changes?
upvoted 0 times
...
Roxane
11 months ago
This is a tricky one. I'm not entirely sure about the relationship between regression and agile projects, but I think it has to do with the rapid pace of change and the need to constantly update and refine the codebase.
upvoted 0 times
...
Amos
11 months ago
I'm pretty confident that it's about message aggregation since it relates to handling multiple policies in a unified manner.
upvoted 0 times
...
Gabriele
1 year 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 year ago
D) There is code churn due to change in business needs over several sprints.
upvoted 0 times
...
Merissa
1 year ago
B) Test automation can cause regression of software in the test environment.
upvoted 0 times
...
Rosendo
1 year ago
A) Test-driven development means that existing functionality is not considered.
upvoted 0 times
...
...
Pilar
1 year 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
1 year ago
That's true, test automation can sometimes introduce unexpected issues when changes are made to the codebase.
upvoted 0 times
...
Bonita
1 year ago
Test automation can cause regression of software in the test environment.
upvoted 0 times
...
Isabella
1 year 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
1 year 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
1 year ago
User 3: But what about the code churn due to change in business needs over several sprints?
upvoted 0 times
...
Raina
1 year ago
User 2: Raina is right, we should just embrace the unexpected failures.
upvoted 0 times
...
Barney
1 year ago
User 1: Haha, option C is a good one! Regression is a 'feature', not a bug.
upvoted 0 times
...
...
Brigette
1 year 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
1 year 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
1 year ago
That's true, test-driven development may not cover all existing functionality.
upvoted 0 times
...
Lezlie
1 year ago
Test automation can also play a role in causing regression of software.
upvoted 0 times
...
Elliott
1 year ago
Yes, the constant change in business needs can definitely lead to code churn.
upvoted 0 times
...
Shalon
1 year ago
Option D seems like the most reasonable answer.
upvoted 0 times
...
...
Gianna
1 year 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
1 year 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
1 year 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