microsoft / microsoft/typespec

[Discussion] Tooling for generating samples, tests, and other assets for client emitters

Open
#9,296 1 comment 1 reaction 1 assignee Claimed by @markcowl View on GitHub
compiler:core design:needed triaged:core
Dominant language
Java
Stars
5.9k
Forks
394
Avg merge
1d 23h
Merged PRs (30d)
104

Description

Creating this issue as a place to discuss tooling for generating samples, tests, and other assets as part of SDK client generation.

We have been exploring this space for Azure SDKs, but would like to get feedback from others using TypeSpec to know if there is a general need/desire for similar tooling.

Some starter questions:

1. Is it better to hand-author samples/tests/etc in one language and then translate to others or to use natural language to describe the scenarios when authoring the spec?
2. What kinds of tests would be most useful (e.g. functional validation of the model shape/payload or end-to-end scenarios of ensuring basic functionality works as expected.)
3. How frequent/expensive is this task? For example, Azure has many (100+) resource management SDKs to support across 5+ languages, but perhaps this is a specific challenge of Azure.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.