Testcraft Studio — office setup and complete file index

Testcraft Studio - office setup and file index

Copy each post's complete code block into the exact file path shown. Do not copy the opening/closing backticks. Save files as UTF-8 using All files, so Windows does not add a .txt extension.

Run the ready frontend without npm installation

Install Node.js if it is not already available.
Create a folder named testcraft-studio with dist and dist/assets subfolders.
Copy these five files from their individual posts:

Open PowerShell in testcraft-studio and run:

node serve.cjs

Open http://127.0.0.1:5175/ and keep PowerShell open during the presentation. Stop the server with Ctrl+C. If that port is occupied, use node serve.cjs 5176 and open http://127.0.0.1:5176/.

The five-file prebuilt option needs no npm installation or internet connection. Optional web fonts fall back to system fonts when offline.

Copy the complete editable frontend

Create the folders:

New-Item -ItemType Directory -Force testcraft-studio | Out-Null
Set-Location testcraft-studio
New-Item -ItemType Directory -Force src, src/pages, public, tests, tests/fixtures, dist, dist/assets | Out-Null

Copy all 51 files below into those folders. Each post contains one file only.

The Excel workbook is binary, so its post contains a lossless base64 text version. Save it as tests/fixtures/Membership_Test_Template.xlsx.base64.txt, then reconstruct the workbook once:

[IO.File]::WriteAllBytes((Join-Path (Get-Location) 'tests/fixtures/Membership_Test_Template.xlsx'), [Convert]::FromBase64String([IO.File]::ReadAllText((Join-Path (Get-Location) 'tests/fixtures/Membership_Test_Template.xlsx.base64.txt'))))

Development and checks

Use Node.js 20.19+ in the 20.x release line or Node.js 22.12+. Installing dependencies needs internet access.

npm.cmd ci
npm.cmd run dev

Open http://127.0.0.1:5175/. To verify and rebuild the frontend:

npm.cmd test
npm.cmd run build
node serve.cjs

Run one server at a time on port 5175. React and React DOM are the only runtime packages; Vite is used for development and production builds.

Sign in and demonstrate the workflow

Choose MCM (Membership and Collateral Management). The public prototype system passwords are team-demo for User and admin-demo for Administrator.

Create a workspace, create its System Baseline with any one Business, Technical, or Functional / Bug Information document, and submit it for Administrator approval. Baseline creation, document edits, and CR merges require approval. Other workflows are available to team Users.

Add reviewed source-linked requirements and CR documents. In Workspace chat, ask document questions or request Technical, Functional, or Business test cases. Follow up to refine the draft, inspect supporting source revisions, and save cases to Test suites or export CSV. Choose a template or upload Excel before generating. The frontend uses a local evidence adapter; the real LLM connection is deferred to the backend phase. Clarifications are optional. Use Knowledge versions to select CR changes, submit a merge, and approve the new baseline as Administrator.

Connections and Data & audit are tabs under Administration. The frontend stores workspace records in the browser. Backend services, agents, production authentication, and server-side approval enforcement are deferred. This transfer contains application code and synthetic fixtures; it does not transfer uploaded documents, private conversations, or browser sessions.

DEV Community