Tests & debugging

Record and verify a browser journey

Turn a manual application check into an editable test, with results and traces.

In this guideBefore you start · PremiumCheck a search form from start to finishUnderstand what happened

Before you start · Premium#

This guide covers tools included in Code Weaver Premium. Sign in to your account in the IDE and check that Premium is active. Without Premium you can still browse, search, edit and save your files.

Check a search form from start to finish#

A browser test repeats a user journey and checks its result. Recording uses Playwright, which generates an editable test file. The Inspector is the window where you review steps and add assertions, for example that an expected result appears.

  1. Start your application, then open Development tools → Browser tests.
  2. If the managed browser is not ready yet, click Install Chromium. Enter the Local application URL, for example http://localhost:5173.
  3. Click Record journey. In the opened browser, fill in the search, click the application button and use the Inspector to assert the displayed result.
  4. Return to Code Weaver, click Finish recording and review the generated code.
  5. Choose a name and click Save test in project. The file is created under .code-weaver/browser-tests/<name>.spec.ts.
  6. Click Run browser test and inspect the case result. Open test opens its source; Debug with Inspector lets you follow its steps.

Understand what happened#

Open the test location from its result. When available, Show screenshot and Open trace display run artifacts; Network requests lists observed calls and Playwright output shows runner messages. A trace records test steps to help reconstruct page behavior.

Example: if a search ends without results, compare the test assertion with the network response and the page in the trace. Correct the application or assertion, save the file and run the test again.

Open original image ↗