diff --git a/src/pages/talks.tsx b/src/pages/talks.tsx
index 0e36f7b..1f65f7a 100644
--- a/src/pages/talks.tsx
+++ b/src/pages/talks.tsx
@@ -4,58 +4,97 @@ import Layout from "@theme/Layout";
 import Talk, { TalkMetadata } from "../components/talks/Talk";
 
 const talks: TalkMetadata[] = [
-    {
-        title: "Packit: RPM integration, all in one",
-        description: (
-            <>
-                Do you want to automate how you build and test your RPM packages?
-                Do you maintain any package in Fedora and want to automate the
-                releases? Or are you just interested in CI/CD on GitHub or GitLab,
-                Fedora and integration of upstream projects with RPM-based Linux
-                distributions? In this session, we are going to deep-dive into
-                features of Packit that can help you do your day-to-day job.
-            </>
-        ),
-        events: [
-            {
-                name: "DevConf.cz",
-                location: "Brno, Czechia",
-                date: new Date(2023, 5, 17),
-            },
-            {
-                name: "DevConf.cz Mini",
-                location: "Brno, Czechia",
-                date: new Date(2023, 2, 31),
-            },
-        ],
-        recordingURL: "https://www.youtube.com/watch?v=FxhXzgxWO18",
-        slidesURL: "https://static.sched.com/hosted_files/devconfcz2023/37/DevConf.cz%20June%202023%20Packit%20talk-1.pdf",
-    },
+  {
+    title: "Shift Left Testing with Packit and Testing Farm",
+    description: (
+      <>
+        <p>
+          In today's fast-paced software development landscape, ensuring the
+          quality and reliability of upstream contributions is crucial. The
+          traditional approach of testing at the end of the development cycle is
+          no longer sufficient. To address this challenge, we present "Shift
+          Left Your Testing with Packit and Testing Farm", a talk that
+          introduces two powerful tools designed to simplify and enhance the
+          testing process for the upstream contributions.
+        </p>
+
+        <p>
+          Packit and Testing Farm provide a dead simple way to build and test
+          your upstream contributions against both public or internal Red Hat
+          testing infrastructure. In this talk, we will explore the capabilities
+          of both tools and demonstrate how they can be seamlessly integrated
+          into your development workflow.
+        </p>
+
+        <p>
+          In addition to the current capabilities, we will share our plans for
+          Packit and Testing.
+        </p>
+      </>
+    ),
+    events: [
+      {
+        name: "QEcamp23",
+        location: "virtual",
+        date: new Date(2023, 10, 19),
+      },
+    ],
+  },
+  {
+    title: "Packit: RPM integration, all in one",
+    description: (
+      <>
+        Do you want to automate how you build and test your RPM packages? Do you
+        maintain any package in Fedora and want to automate the releases? Or are
+        you just interested in CI/CD on GitHub or GitLab, Fedora and integration
+        of upstream projects with RPM-based Linux distributions? In this
+        session, we are going to deep-dive into features of Packit that can help
+        you do your day-to-day job.
+      </>
+    ),
+    events: [
+      {
+        name: "DevConf.cz",
+        location: "Brno, Czechia",
+        date: new Date(2023, 5, 17),
+      },
+      {
+        name: "DevConf.cz Mini",
+        location: "Brno, Czechia",
+        date: new Date(2023, 2, 31),
+      },
+    ],
+    recordingURL: "https://www.youtube.com/watch?v=FxhXzgxWO18",
+    slidesURL:
+      "https://static.sched.com/hosted_files/devconfcz2023/37/DevConf.cz%20June%202023%20Packit%20talk-1.pdf",
+  },
 ];
 
 const title = "Talks";
 const description = "Featured talks I presented on various events.";
 
 export default function Talks(): JSX.Element {
-    return (
-        <Layout title={title} description={description}>
-            <main className="container container--fluid margin-vert--lg">
-                <h1>{title}</h1>
-                <p>{description}</p>
+  return (
+    <Layout title={title} description={description}>
+      <main className="container container--fluid margin-vert--lg">
+        <h1>{title}</h1>
+        <p>{description}</p>
 
-                <div className="row">
-                    {talks.map((talkData) => (
-                        <Talk key={talkData.title} {...talkData} />
-                    ))}
-                </div>
+        <div className="row">
+          {talks.map((talkData) => (
+            <Talk key={talkData.title} {...talkData} />
+          ))}
+        </div>
 
-                <hr/>
-                <p>
-                    Credits to <a href="https://kosiec.dev/" target="_blank">
-                    Paweł Kosiec</a> for implementing his own React components
-                    for talks.
-                </p>
-            </main>
-        </Layout>
-    );
-}
\ No newline at end of file
+        <hr />
+        <p>
+          Credits to{" "}
+          <a href="https://kosiec.dev/" target="_blank">
+            Paweł Kosiec
+          </a>{" "}
+          for implementing his own React components for talks.
+        </p>
+      </main>
+    </Layout>
+  );
+}