Add workflow for running e2e on main vercel deployment

Author: ostenbom

package.json

@@ -1,5 +1,6 @@
 {
 	"private": true,
+	"packageManager": "pnpm@10.15.0",
 	"scripts": {
 		"dev": "next dev --turbopack",
 		"build": "next build --turbopack",
@@ -44,6 +45,6 @@
 		"@biomejs/biome": "^2.2.2",
 		"@playwright/test": "^1.55.0",
 		"@types/bun": "^1.2.21",
-		"endform": "^0.35.0"
+		"endform": "^0.35.1"
 	}
 }

pnpm-lock.yaml

@@ -45,7 +45,7 @@ export const tutorialConfig: TutorialConfig = {
 			name: "stage-3-endform-integration",
 			title: "Running tests with Endform",
 			order: 3,
-			newPaths: [],
+			newPaths: [".github/workflows/endform-tests-on-main.yml"],
 		},
 		{
 			name: "stage-4-completed",

tutorial.config.ts

@@ -1,5 +1,5 @@
 ---
-title: From cowboy to confidence
+title: Using Playwright for end-to-end testing - From cowboy to confidence
 description: Outline of the Endform saas tutorial, where we will take an untested saas application and build a Playwright test suite for it.
 sidebar:
   order: 1

tutorial/stage-0-baseline/from-cowboy-to-confidence.mdx

@@ -65,7 +65,7 @@ Here, Playwright took 30 seconds, and Endform took 25 seconds.
 
 If we plot the results of different repeat counts, we get:
 
-<Image src={TestTimeChart} alt="A chart of the test time for different repeat counts" width={600} />
+<Image src={TestTimeChart} alt="A chart of the test time for different repeat counts" width={800} />
 
 Once we start to add more tests (or if the tests had taken longer to run), Playwright will keep slowing your suite down,
 while Endform will keep the speed constant.