[TE-14105] docs: add Test Data Generation section to enterprise-ready

[sandeepyadav-lt]

Summary

• Adds a new Test Data Generation section to the Enterprise Readiness page covering synthetic data generation, data masking, and parameterization. Section sits before Reporting & Analytics with a matching top-of-page nav chip.
• New landing page at /support/docs/test-data-generation/ that summarizes all three capabilities and links to the existing deeper docs (KaneAI Datasets, Variables & Parameters, Network Data Masking, HyperExecute Lambda Masking).
• Includes 4 screenshots reused from assets/images/kane-ai/features/datasets and parameters — no new image assets added. Data Masking has no screenshot since the source docs are text-only.

Tracked in TE-14105.

Files

• New: docs/test-data-generation.md
• Modified: docs/enterprise-ready.md (new section + nav chip)

Test plan

• npm start compiles cleanly (verified on port 3001 — Compiled successfully in 32.81s, no broken-link warnings, no missing-image warnings)
• Both URLs return 200: /support/docs/enterprise-ready/ and /support/docs/test-data-generation/
• Hot reload after image edits also compiled cleanly (~1.5s)
• All internal link targets verified to exist as .md files
• Reviewer to eyeball rendered pages on the deploy preview

Notes for reviewers

• The new page is not added to sidebars.js — it's a standalone enterprise-evaluation page, same model as enterprise-ready.md. Happy to wire it into the sidebar if you'd prefer.
• The Data Masking subsection deliberately has no screenshot. Two source docs (network-data-masking.md, hyperexecute-release-notes-2-3-1.md) ship text-only and there are no masking screenshots in /assets/images. Easy to add later if a "before/after masked log" screenshot is wanted.

🤖 Claude conversation log

User: Wants to add a new "Test Data Generation (2.2)" section to the existing enterprise-ready page with three sub-capabilities — synthetic data generation, data masking, parameterization — referencing four existing docs: kane-ai-using-datasets, kaneai-variables-and-parameters, network-data-masking, and the #mask-your-sensitive-data anchor on hyperexecute-release-notes-2-3-1. Provided three KaneAI UI screenshots showing the Parameters table view, Create Parameter dialog, and the "Convert as" Parameter/Variable/Secret popup. Asked Claude to ask clarifying questions if needed and to match tone/scope of the existing enterprise-ready doc.

Claude: Read docs/enterprise-ready.md to understand the section pattern (heading → 2-sentence overview → bullet list of capabilities → list of doc links → --- separator) and confirmed the four reference docs all exist locally. Asked three clarifying questions: scope (just a section vs. section + landing page vs. section + 3 sub-pages), placement (after Product Security, after Data Protection, before Change Management), and whether to keep the "(2.2)" in the heading.

User: Picked "Section + 1 new landing page", placement "before Reporting & Analytics", and "Drop (2.2) — use 'Test Data Generation'".

Claude: Created docs/test-data-generation.md with frontmatter, schema.org breadcrumb, three capability sections, footer breadcrumb. Added a "Test Data Generation" chip to the top nav button row in enterprise-ready.md between Integrations and Reporting & Analytics, and inserted the matching ## Test Data Generation section in the same position with capabilities + documentation lists. Verified all link slugs exist via filesystem check.

User: "run the build to verify"

Claude: Ran npm run build with NODE_OPTIONS heap bump. Build hit ENOSPC: no space left on device repeatedly during static file generation. df -h showed /System/Volumes/Data at 100% with only 1.9 GB free, build dir already 1.2 GB. No content errors fired before disk filled — failure was purely disk-space.

User: Interrupted to redirect: "can you simply run npm start or dev"

Claude: Started npm start in background. Background task completed with exit code 0 — odd for a long-running dev server. Inspected the log: prestart scripts ran fine (220 API endpoints generated), but [ERROR] Something is already running on port 3000. Curling localhost:3000 confirmed it was a different app ("LambdaTest Analytics", stage-beta-analytics.lambdatestinternal.com), not the docs site. Killed the monitor and restarted with npx docusaurus start --port 3001 --no-open.

Claude: Waited for compile. [SUCCESS] Docusaurus website is running at: http://localhost:3001/support/, then [webpackbar] ✔ Client: Compiled successfully in 32.81s. Zero errors, zero warnings, no broken-link reports. Both new URLs returned 200. Noted that curl content-grep didn't find markers because Docusaurus dev mode renders client-side — the clean compile + 200s + no warnings was the real signal.

User: "can you add images in the overview doc"

Claude: Surveyed available images. Found 8 images under assets/images/kane-ai/features/datasets/ and 10 under assets/images/kane-ai/features/parameters/. No masking-specific images exist anywhere in the repo. Picked datasets/1.png (Parameters table) + datasets/5.png (Autofill with AI) for the Synthetic Data Generation section, and parameters/1.png (Convert as popup) + parameters/3.png (Create Parameter dialog) for the Parameterization section. Skipped Data Masking since no relevant images exist. Webpack hot-reloaded both edits in ~1.5s with no errors.

User: "create a simple task in TE board in jira, keep it simple and easy to understand"

Claude: Looked up cloudId via getAccessibleAtlassianResources, then getVisibleJiraProjects with searchString "TE". Found project TE = "TestMu Engineering" (id 11975). First attempt to create a "Task" issue type failed: The issue type selected is invalid. Listed available issue types via getJiraProjectIssueTypesMetadata — TE doesn't have a standard "Task" type. Available top-level types: Epic, Story, Bug, Simple Task. Recreated with issueTypeName: "Simple Task" and it succeeded. Returned TE-14105. Saved a memory note (memory/jira_te_project.md) so future Jira creates in TE skip the failed "Task" attempt.

User: Invoked /commit-push-pr.

Claude: Verified working tree (docs/enterprise-ready.md modified, docs/test-data-generation.md new, .claude/ untracked but local-only). Created feature branch docs/test-data-generation off stage, staged only the two doc files (skipped .claude/), committed with conventional docs: prefix matching project history, pushed to fork remote sky (sandeepyadav-lt/documentation), and opened this PR against LambdaTest/documentation:stage.

🤖 Generated with Claude Code