testdriverai 6.0.30 → 6.0.31

package/docs/getting-started/playwright.mdx

@@ -19,10 +19,12 @@ We'll be incrementally converting Playwright's example test from the sample code
 
 ```typescript tests/example.spec.ts icon=square-js
 // Before
-test("get started link", async ({ page, testdriver }) => {
+test("get started link", async ({ page }) => {
   await page.goto("https://playwright.dev/");
-  await testdriver(page).act("Click the 'Get started' link");
-  await expect(page).toMatchPrompt("'Installation' heading is visible");
+  await page.getByRole("link", { name: "Get started" }).click();
+  await expect(
+    page.getByRole("heading", { name: "Installation" }),
+  ).toBeVisible();
 });
 ```
 
@@ -30,6 +32,8 @@ To using natural language with TestDriver:
 
 ```typescript tests/example.spec.ts icon=square-js
 // After
+import { test } from "@testdriver.ai/playwright";
+
 test.describe("get started link", () => {
   test.beforeEach(async ({ page }) => page.goto("https://playwright.dev/"));
   test.agent(`
@@ -44,10 +48,7 @@ test.describe("get started link", () => {
 <Steps>
   <Step title="Create a TestDriver Account">
     You will need a [TestDriver Pro](https://app.testdriver.ai/team) account (\$20/month) to get an API key.
-
-    <Card title="Sign Up for TestDriver" icon="user-plus" horizontal href="https://app.testdriver.ai/team">
-      
-    </Card>
+    <Card title="Sign Up for TestDriver" icon="user-plus" horizontal href="https://app.testdriver.ai/team" />
   </Step>
   <Step title="Set up your environment">
     Copy your API key from [the TestDriver dashboard](https://app.testdriver.ai/team), and set it as an environment variable.
@@ -64,6 +65,7 @@ test.describe("get started link", () => {
         ```
       </Tab>
     </Tabs>
+
   </Step>
 </Steps>
 
@@ -76,7 +78,7 @@ test.describe("get started link", () => {
 
       **If you're new to Playwright, you should follow their guide first.**
     </Info>
-    In an new folder or existing run:
+    In a new folder or an existing, run:
 
     <Tabs>
       <Tab title="npm">
@@ -127,6 +129,7 @@ test.describe("get started link", () => {
         ```
       </Tab>
     </Tabs>
+
   </Step>
 </Steps>
 
@@ -153,6 +156,7 @@ test.describe("get started link", () => {
         ```
       </Tab>
     </Tabs>
+
   </Step>
   <Step title="Run Playwright">
     Before we start using TestDriver in our tests, run Playwright in [UI Mode](https://playwright.dev/docs/test-ui-mode):
@@ -178,6 +182,7 @@ test.describe("get started link", () => {
 
     Clicking the ▶️ button should successfully run the tests in the UI,
     just as they did before with `playwright test` in the CLI.
+
   </Step>
   <Step title="Import TestDriver">
     For the sake of simplicity, we'll be working with one test file for now.
@@ -195,6 +200,7 @@ test.describe("get started link", () => {
     <Tip>
       Click the <Icon icon="eye" /> button to automatically re-run tests on save.
     </Tip>
+
   </Step>
 </Steps>
 
@@ -262,14 +268,15 @@ Now, our test uses natural language to both describe & locate the element.
 <Tip>
   In the example above, you can still use Playwright to assert that the element is indeed a link for accessibility:
 
-  ```typescript tests/example.spec.ts icon=square-js
-  const link = await testdriver(page).locate("Get started link");
-  // [!code ++]
-  expect(link).toHaveRole("link");
-  await link.click();
-  ```
+```typescript tests/example.spec.ts icon=square-js
+const link = await testdriver(page).locate("Get started link");
+// [!code ++]
+expect(link).toHaveRole("link");
+await link.click();
+```
+
+This way you can write user-centric tests _and_ validate the implementation.
 
-  This way you can write user-centric tests _and_ validate the implementation.
 </Tip>
 
 ### Performing actions with `testdriver.act`
@@ -318,7 +325,8 @@ Instead of writing the test implementation, we've used [`test.describe`](https:/
 but replaced the `test` itself with `test.agent`.
 
 <Tip>
-  Use `test.beforeEach` to prepare the page for the agent (e.g. [`page.goto`](https://playwright.dev/docs/api/class-page#page-goto), calling
+  Use `test.beforeEach` to prepare the page for the agent (e.g.
+  [`page.goto`](https://playwright.dev/docs/api/class-page#page-goto), calling
   an API to create a user). Use
   [`test.afterEach`](https://playwright.dev/docs/api/class-test#test-after-each)
   to clean up after the agent (e.g. `page.close`) or perform additional logic
@@ -327,4 +335,4 @@ but replaced the `test` itself with `test.agent`.
 
 ## Conclusion
 
-With `@testdriver.ai/playwright`, you can use as much or as little of Playwright's _or_ TestDriver's API as you need to validate correctness. It's up to you!
+With `@testdriver.ai/playwright`, you can use as much or as little of Playwright's _or_ TestDriver's API as you need to validate correctness. It's up to you!

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "testdriverai",
-  "version": "6.0.30",
+  "version": "6.0.31",
   "description": "Next generation autonomous AI agent for end-to-end testing of web & desktop",
   "main": "index.js",
   "bin": {