Parent testing issue: #1
Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/NV-004-domain-faker-top-level-help-thin.md
Testing artifact folder: https://github.com/eviltester/anywaydata-ai-testing/tree/main/docs/testing/20260625/issue-230-001
Original grid-table-editor story: eviltester/grid-table-editor#230
Original grid-table-editor PR: eviltester/grid-table-editor#247
The detailed defect report from the testing artifact is copied below.
NV-004: Top-level domain/faker help lacks params/examples compared with core command help
Severity: Low
Status: confirmed in negative-validation and final-review passes.
Environment
Steps to Reproduce
- Open the deployed generator or app Test Data panel.
- In the schema row, rotate the field type through enum, literal, regex, domain, and faker.
- Inspect the top-level help for each type.
Expected Result
Domain and faker top-level help should orient users with at least the same level of params/example guidance as enum, literal, and regex, especially because domain/faker commands now open a rich method picker.
Actual Result
Enum, literal, and regex help show schema params, parameter descriptions, and examples. Domain and faker help only show a short category description plus a Learn more link.
Triage Decision
The description for top level faker should not read "Faker commands generate realistic random values such as names, addresses, and dates." instead - "faker helper commands allow use of more complex generation than the domain commands (see help for details) e.g." and then add an example of helpers range to number.
Add some command examples in the Domain tippy text to expand out the tippy and make every top level tippy have some examples.
Notes
The method picker gives detailed help after opening and selecting a command, so this is not a blocker. It is a discoverability/content consistency issue around the changed help surface.
Parent testing issue: #1
Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/NV-004-domain-faker-top-level-help-thin.md
Testing artifact folder: https://github.com/eviltester/anywaydata-ai-testing/tree/main/docs/testing/20260625/issue-230-001
Original grid-table-editor story: eviltester/grid-table-editor#230
Original grid-table-editor PR: eviltester/grid-table-editor#247
The detailed defect report from the testing artifact is copied below.
NV-004: Top-level domain/faker help lacks params/examples compared with core command help
Severity: Low
Status: confirmed in negative-validation and final-review passes.
Environment
../logs/negative-validation-test-log.md,../support/final-review-executions.json,../screenshots/negative-04-faker-help.pngSteps to Reproduce
Expected Result
Domain and faker top-level help should orient users with at least the same level of params/example guidance as enum, literal, and regex, especially because domain/faker commands now open a rich method picker.
Actual Result
Enum, literal, and regex help show schema params, parameter descriptions, and examples. Domain and faker help only show a short category description plus a Learn more link.
Triage Decision
The description for top level faker should not read "Faker commands generate realistic random values such as names, addresses, and dates." instead - "faker helper commands allow use of more complex generation than the domain commands (see help for details) e.g." and then add an example of helpers range to number.
Add some command examples in the Domain tippy text to expand out the tippy and make every top level tippy have some examples.
Notes
The method picker gives detailed help after opening and selecting a command, so this is not a blocker. It is a discoverability/content consistency issue around the changed help surface.