<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Melissa Milligan</title>
    <description>The latest articles on DEV Community by Melissa Milligan (@melissa_milligan_4be2746d).</description>
    <link>https://dev.to/melissa_milligan_4be2746d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3906492%2F3ba22726-6074-4212-a442-88f05085838d.jpg</url>
      <title>DEV Community: Melissa Milligan</title>
      <link>https://dev.to/melissa_milligan_4be2746d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/melissa_milligan_4be2746d"/>
    <language>en</language>
    <item>
      <title>CypressConf 2026: Answering the signal</title>
      <dc:creator>Melissa Milligan</dc:creator>
      <pubDate>Mon, 26 Oct 2026 16:25:16 +0000</pubDate>
      <link>https://dev.to/cypress/cypressconf-2026-answering-the-signal-41bg</link>
      <guid>https://dev.to/cypress/cypressconf-2026-answering-the-signal-41bg</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fivaz7i81crcwurbousbc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fivaz7i81crcwurbousbc.png" alt="Event Recap, CypressConf 2026 Answering the Signal" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;CypressConf 2026 is a wrap! Thank you to everyone who joined us for three days of talks and hands-on workshops. This year’s theme, The Signal Is Up, asked a question every team knows well: how do you know a release is ready when the build is green? &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;From the founders: Quality in the era of the agentic SDLC&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;In the founder session, Brian Mann, Founder of Cypress.io, and Jennifer Shehane, Co-founder and Head of Product, talked about using AI so teams spend more time building and less time cleaning up. Jennifer showed how recent releases like Cypress Tap, the Cloud CLI, Cloud MCP and Webhooks give agents the context to test and debug on their own.&lt;/p&gt;

&lt;p&gt;Brian looked at the road ahead. He estimated that most teams have handed only 5% to 20% of their work to agents so far, and that work needing judgment will be the hardest to hand off. For agents to do that work well they need access to your systems, an understanding of what your data means, and a way to tell whether they got it right. His closing point framed the whole conference. The job of software quality has always been deriving and validating intent: did we ship the thing we meant to ship? Agents change the form factor. They don't change the job. Brian has spent the past year exploring how teams can confirm that what they ship matches what they meant to build. Want to help shape it?&lt;a href="https://on.cypress.io/cyconf-dpp?ref=dev-to" rel="noopener noreferrer"&gt;&lt;u&gt;Join the design partner program&lt;/u&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Lessons from industry leaders&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Across the sessions, speakers kept coming back to the same idea: a signal is only useful if you can trust it. Here’s what we learned.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Green is not the goal&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A passing suite doesn’t always mean a release is safe, because coverage numbers and pass rates can hide shallow assertions and flaky tests. Judge your tests by whether they would catch a real bug and whether you’d trust them to make the release call, and keep checking critical paths after they ship.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Governing is the new writing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Agents can write tests in seconds, so more of the work now goes into reviewing what they produce. Give your agents clear written rules, keep each task small enough to review properly, and keep critical tests in version-controlled code that a person has checked.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Debugging at the speed of the signal&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Most of the time spent on a failed run goes into working out whether it’s a real bug, a known flake or an environment problem. Give people and agents the full picture, including test history, Test Replay and error patterns, and rerun only the tests that failed.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Catch the sessions&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;All sessions will be published to the &lt;a href="https://www.youtube.com/playlist?list=PLPPb-bn9jZmI&amp;amp;utm_source=blog&amp;amp;utm_medium=cypress.io&amp;amp;utm_content=cypressconf2026" rel="noopener noreferrer"&gt;&lt;u&gt;Cypress YouTube channel&lt;/u&gt;&lt;/a&gt; in the coming weeks. In the meantime, put the Cypress AI features to work on your own runs and strengthen your signal. &lt;/p&gt;

&lt;p&gt;Thank you to our speakers and to everyone who kept the chat busy for three days. We can’t wait to see you next year!&lt;/p&gt;

</description>
      <category>cypress</category>
      <category>codequality</category>
      <category>sdlc</category>
      <category>testing</category>
    </item>
    <item>
      <title>Cypress Ambassador Spotlight: Boris Selivanov</title>
      <dc:creator>Melissa Milligan</dc:creator>
      <pubDate>Fri, 24 Jul 2026 13:43:32 +0000</pubDate>
      <link>https://dev.to/cypress/cypress-ambassador-spotlight-boris-selivanov-2lbp</link>
      <guid>https://dev.to/cypress/cypress-ambassador-spotlight-boris-selivanov-2lbp</guid>
      <description>&lt;p&gt;&lt;strong&gt;What motivates you to be a Cypress Ambassador?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I see being an Ambassador as the ultimate form of asynchronous collaboration. My goal is to share things that move the needle for other engineers. By comparing how different teams solve the same testing problems, we can turn isolated project victories into shared wins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do you currently help others that are either using Cypress or interested in using Cypress?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'm the person teammates ping when a test goes flaky or they're not sure how to approach a complex scenario. I always try to answer with a reusable pattern rather than a one-off fix so the knowledge scales past me. A lot of that is helping people pick selectors that survive a redesign, semantic and stable, over cosmetic and brittle.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is your favorite Cypress feature?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;cy.intercept(). It's the ultimate tool for eliminating flake caused by unstable backend environments or slow APIs. Being able to intercept, modify, or stub network traffic means you can test frontend behavior under any condition imaginable, instantly. It guarantees your tests are deterministic, isolated, and entirely repeatable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is your favorite "Cypress Best Practice" and why?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Never using arbitrary cy.wait(ms). Hard waits are a confession that you don't trust your tooling. They either slow every run down or paper over a real race condition. Leaning on retry-ability and cy.intercept() aliases instead means the suite waits exactly as long as it needs to, no more, no less.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outside of work, what are your favorite things to do (hobbies, passions, etc.)?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Catching FIFA World Cup matches with friends. It's the perfect way to unwind and watch a defensive line get tested for a change, instead of my own automation suite.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is one professional milestone you are proud of?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Building stable automation frameworks from scratch and successfully scaling that knowledge across large, cross-functional teams. Throughout my career, my favorite milestones haven't just been writing clean architectural patterns, but leading training sessions for 20+ engineers and clients to get them comfortable with test automation. Demystifying complex testing concepts and giving teams the leverage to confidently own their builds is exactly what drives me.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;For new users - what is the best way to "get started" with Cypress?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Skip the boring configuration routines. Just run npm install cypress, open the runner, and write a real test against your actual app: visit a page, fill a form, submit, and assert the result. Letting the native retry-ability handle the async waiting while watching it interact with your live, real-world codebase is the absolute fastest way to make the framework click.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is your favorite quote or saying?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;"It works on my machine."&lt;/p&gt;

</description>
      <category>cypress</category>
      <category>ambassador</category>
      <category>testing</category>
      <category>development</category>
    </item>
  </channel>
</rss>
