<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Tessa Changelog | What&#39;s New in Tessa</title>
		<link>https://tessa-testing.ch/changelog/</link>
		<description>What changed in Tessa with each release, for teams that test Android, iOS, web and desktop apps.</description>
		<language>en-US</language>
		<lastBuildDate>Wed, 16 Sep 2026 21:21:11 +0200</lastBuildDate>
		<atom:link href="https://tessa-testing.ch/changelog/index.xml" rel="self" type="application/rss+xml" />
		<item>
			<title>Desktop tests pause while someone uses the computer</title>
			<link>https://tessa-testing.ch/changelog/2026-09-16-desktop-pause/</link>
			<pubDate>Wed, 16 Sep 2026 21:21:11 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-09-16-desktop-pause/</guid>
			<description>A desktop test announces itself with a countdown and pauses when someone takes the mouse or keyboard.</description>
			<content:encoded><![CDATA[<p>A banner counts down three seconds before the test starts and has a Stop button. The test resumes three seconds after the last input. Paused time does not count against the test&rsquo;s time limit.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Tessa searches and files issues from the chat</title>
			<link>https://tessa-testing.ch/changelog/2026-09-16-issues-from-chat/</link>
			<pubDate>Wed, 16 Sep 2026 13:20:01 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-09-16-issues-from-chat/</guid>
			<description>The Tessa Assistant searches your issue tracker live and files an issue from what you describe.</description>
			<content:encoded><![CDATA[<p>Describe what you saw, and Tessa writes the issue with device, operating system and build. It shows likely duplicates before you confirm. Tessa only changes issues it filed itself.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Tests run on real iPhones signed by your own Apple team</title>
			<link>https://tessa-testing.ch/changelog/2026-09-13-iphone-signing/</link>
			<pubDate>Sun, 13 Sep 2026 12:01:57 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-09-13-iphone-signing/</guid>
			<description>The Tessa Executor on your Mac signs and installs Apple&#39;s test agent, and your signing key never leaves that Mac.</description>
			<content:encoded><![CDATA[<p>Plug in the iPhone, and the executor registers it with Apple and renews the certificate and profile. You enter your team&rsquo;s key once per Mac. You need a paid Apple Developer Program team.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Hooks run your own code before and after a test</title>
			<link>https://tessa-testing.ch/changelog/2026-09-13-hooks/</link>
			<pubDate>Sun, 13 Sep 2026 12:00:00 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-09-13-hooks/</guid>
			<description>Short JavaScript on your own Tessa Executor runs before a test, after it, or both.</description>
			<content:encoded><![CDATA[<p>A hook can prepare test data, clean up afterwards, or call any webhook. Workspace owners write the hooks, and testers attach them to scenarios. A hook that fails before the test stops it before the app opens, and the failure does not count as a regression. Hooks only run on computers whose owner has allowed them.</p>
]]></content:encoded>
		</item>
		<item>
			<title>New workspaces reach their first test on a setup board</title>
			<link>https://tessa-testing.ch/changelog/2026-09-10-setup-board/</link>
			<pubDate>Thu, 10 Sep 2026 15:23:37 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-09-10-setup-board/</guid>
			<description>The dashboard guides a new workspace step by step until Tessa has explored the app and run a test it drafted.</description>
			<content:encoded><![CDATA[<p>The owner connects an AI provider and a device, creates a project and adds a build or URL. Tessa then explores the app and runs the first test it drafts. People invited later get a welcome panel.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Teams can start Tessa Cloud on their own with 14 days free</title>
			<link>https://tessa-testing.ch/changelog/2026-08-30-tessa-cloud/</link>
			<pubDate>Sun, 30 Aug 2026 20:33:47 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-08-30-tessa-cloud/</guid>
			<description>A team signs up with Google or GitHub and has its own workspace within a minute.</description>
			<content:encoded><![CDATA[<p>The first 14 days are free. After that the team picks a monthly plan on the <a href="https://tessa-testing.ch/pricing/">pricing page</a> and can cancel at any time. An owner can export the whole workspace in one click, in every account state.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Tessa 1.0 turns a failed test into a drafted issue</title>
			<link>https://tessa-testing.ch/changelog/2026-08-18-tessa-1-0/</link>
			<pubDate>Tue, 18 Aug 2026 11:19:55 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-08-18-tessa-1-0/</guid>
			<description>Tessa goes into production and connects to your issue tracker, so a failed test becomes a drafted issue.</description>
			<content:encoded><![CDATA[<p>Tessa lists open issues that look like the same problem before anyone files a new one. When a failure comes back, Tessa comments on the existing issue. A failure after the issue was closed is flagged as a regression.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Test teams share one workspace that learns their app</title>
			<link>https://tessa-testing.ch/changelog/2026-08-13-workspaces/</link>
			<pubDate>Thu, 13 Aug 2026 15:39:15 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-08-13-workspaces/</guid>
			<description>Tessa gains organisations with their own sign-in, and every test adds screens to an App Map of the product.</description>
			<content:encoded><![CDATA[<p>Each organisation&rsquo;s data is kept apart from the others. The device&rsquo;s screen shows live during a test, and a dashboard sorts results by what needs attention. The App Map shows what tests have not covered yet, and Tessa drafts scenarios for those gaps on request.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Tessa moves to a server and starts testing web apps</title>
			<link>https://tessa-testing.ch/changelog/2026-04-14-server-and-web/</link>
			<pubDate>Tue, 14 Apr 2026 12:50:00 +0200</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-04-14-server-and-web/</guid>
			<description>A central server lets tests start from the browser and run on several devices in parallel.</description>
			<content:encoded><![CDATA[<p>An executor connects the devices to the server. Schedules start tests without anyone at the desk. Web apps are tested by their URL, Android and iOS apps as uploaded builds.</p>
]]></content:encoded>
		</item>
		<item>
			<title>Tessa starts as a desktop app that tests phones from plain language</title>
			<link>https://tessa-testing.ch/changelog/2026-03-06-first-beta/</link>
			<pubDate>Fri, 06 Mar 2026 16:48:26 +0100</pubDate>
			<guid>https://tessa-testing.ch/changelog/2026-03-06-first-beta/</guid>
			<description>In the private beta a tester describes a flow in plain words and watches AI drive a connected phone.</description>
			<content:encoded><![CDATA[<p>Scenarios are written in a structured editor, with steps and their expected results. Tessa blocks destructive actions during a test. Today Tessa runs as a server with an interface in the browser.</p>
]]></content:encoded>
		</item>
	</channel>
</rss>
