> ## Documentation Index > Fetch the complete documentation index at: https://docs.peepsai.com/llms.txt > Use this file to discover all available pages before exploring further. # Create and import tests > Create new test cases and their scripts, or bring your existing Playwright tests into Peeps with their scripts intact. Your agent shows you every change before it makes it and waits for your approval. You ask in plain English; the examples below are the kind of thing you might say. ## Create tests > Do we have Peeps tests for password reset? * Create new test cases * Generate and publish a script for a test case * Check how that generation is going Four ways in, one engine — coverage checks, branch diffs, single gaps, and bringing over existing Playwright tests. ## Import existing Playwright tests > Import these Playwright tests into Peeps, keeping my scripts. * Import JavaScript, TypeScript or Python Playwright files as new test cases, keeping each script exactly as written * Check how an import is going, and cancel it Each test in a file becomes its own test case. You approve three times: the exact files to import, the review of each case, and publishing them. If a file contains a credential, your agent asks before moving it into a variable in a non-production environment, and imports the file with a placeholder in its place. Your files on disk are never changed. Nothing runs until you ask for a run. Other frameworks, such as Cypress or Selenium, need converting to Playwright first. An import creates new test cases only; to replace the script of a test case you already have, add a new script version instead.