HomeinsightsAI in the SDLC: Accelerating delivery without losing trust
quality assurance & testing
AI in the SDLC: Accelerating delivery without losing trust
Alexandre Thibaud, Senior Consultant at Itecor · November 19, 2000
AI does not reduce the need for quality. It changes where quality matters most across the SDLC. Teams spend less time creating artefacts and more time verifying that what is generated genuinely meets business needs, complies with expected requirements, and does not introduce new risks.
A promising prospect, certainly, but how can organisations leverage AI without losing control or confidence? Drawing on his hands-on experience, our expert shares the benefits observed in the field, the most common pitfalls, and the changes in practices that enable teams to take advantage of AI while maintaining high-quality standards.
To move beyond the promises and focus on practical realities, we spoke with Alexandre Thibaud, Quality Engineering & Testing Leader. For more than twenty years, he has helped organisations improve their software quality practices, from test automation to large-scale QA transformation.
His view is clear: AI is accelerating software delivery, but it is also increasing the need for a rigorous approach to quality, risk management, and governance.
Before AI tools arrived, what did a typical week look like? Where did most of your time go?
Honestly, a large share went into producing and maintaining artefacts: writing and rewriting test cases, keeping traceability matrices up to date, building status reports by hand from tool exports, and chasing people to clarify requirements. Automation work was often more maintenance than creation, fixing locators, stabilising flaky tests. The truly analytical part (risk analysis, test strategy, challenging a requirement in a workshop) was maybe [a quarter] of the week, and it was always the first thing squeezed when deadlines got tight.
What has changed, phase by phase
How has AI changed writing and maintaining automated tests? How much time does it really save?
For writing, the gain is real: scaffolding a Playwright test, a page object, or a CI workflow goes two to three times faster. Net of corrections, I’d say 30-50% on creation, much less on maintenance. Generated code often uses fragile locators, hard-coded waits, or assertions that only check the page loaded. Fixing that takes time, and if you don’t fix it you’ve just produced flaky tests faster. The real saving comes when you give the model a strong framework and conventions to follow, not when you ask it to start from scratch.
The new risks
Developers now produce much more code with AI. What has this done to the volume and type of defects?
More code means more change per sprint, so more regression risk, and test capacity doesn’t scale at the same rate. The defects I see shift away from typos and obvious crashes, which AI rarely makes, toward subtler issues: logic that is plausible but wrong for this business, inconsistent handling between similar features, and weak error handling. The code compiles, passes its own unit tests, and still does the wrong thing.
The process and the team
Some companies think AI will let them reduce testing or replace testers. What has actually happened?
Where I’ve worked, teams that cut testers saw the number of tests go up and confidence go down. Developers using AI produce lots of tests, but mostly confirming what they built, not challenging it, the tester’s independent viewpoint disappears. What works is a smaller number of more senior testers, focused on strategy, risk and review, with AI absorbing the repetitive production work. That’s a change of profile, not an elimination.
The profession
Which tester skills have become more valuable, and which less important?
More valuable: risk analysis, domain knowledge, critical review, test design techniques (you need them to judge what AI proposes), and the ability to explain a quality risk to a manager. Also a new one: knowing how to instruct and constrain a model, giving it context, rules and examples. Less important: writing test steps by hand, manual formatting of reports, and memorising tool syntax. The paradox is that fundamentals like boundary analysis matter more, not less, because you can’t review what you don’t understand.
What would you tell a manager who wants to introduce AI into testing tomorrow?
First: pick one painful, measurable problem (story quality, test design time, failure triage) and measure the baseline before you start. Second: settle data governance up front: where data goes, which model, under whose keys. Third: keep a human review step and train people in it. Avoid: buying a tool before defining the problem, measuring success by number of tests generated, and cutting testers in the same quarter you introduce AI. You’d lose the people who know whether the output is any good.
Looking ahead
Is there a story from your own work that sums up how AI is changing quality?
While building an AI-assisted reporting tool for Azure DevOps, the generated executive summary of a test campaign read “overall quality is satisfactory” directly above a NO-GO verdict computed from the actual results. Every sentence was well written. It was simply wrong, and a busy manager reading only the summary would have shipped. We fixed it so the narrative can never contradict the data. For me that’s the whole story: AI writes fluently, and the tester’s job is to make sure fluent is also true.
One of the most important takeaways from this interview is that AI does not reduce the need for quality. It shifts its centre of gravity. Where teams once spent a significant portion of their time producing code, tests, or documentation, they must now focus on ensuring that what is generated is relevant, consistent, and genuinely aligned with business needs. The risk is no longer a lack of content or insufficient test coverage. The real risk lies in placing trust too quickly in outputs that appear convincing. As Alexandre Thibaud points out, a fluent, well-written, or technically valid result is not necessarily the right one.
AI enables teams to move faster. Quality remains what allows them to move forward with confidence. It is precisely in balancing acceleration, risk control, and quality assurance that Itecor delivers value.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__hssrc
Session
This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.
_GRECAPTCHA
5 months 27 days
This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
JSESSIONID
session
New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
__hssc
30 minutes
HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
__hstc
1 year 24 days
This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_ga_JYCPSB48B8
2 years
This cookie is installed by Google Analytics.
_gat_gtag_UA_*
1 minute
Google Analytics sets this cookie to store a unique user ID.
_gid
1 day
Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously.
CONSENT
16 years 2 months 25 days 10 hours
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
hubspotutk
1 year 24 days
This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
IDE
1 year 24 days
Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
Session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.
yt-remote-device-id
never
YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.