draft, add smoke-http-specs for smoke tests #6981
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
All changed packages have been documented.
|
|
You can try these changes here
|
weidongxu-microsoft
requested review from
bterlson,
markcowl,
timotheeguerin,
witemple-msft,
chrisradek and
AlitzelMendez
as code owners
There was a problem hiding this comment.
is the goal of this probject to have the samples we talked about a while ago that every emitter could share?
There was a problem hiding this comment.
It was to include the samples from typespec-e2e.
We've agreed that they should not be spector case. The issue chose to call them smoke test.
I haven't figured out with Allen on what is the best approach is, for matching a generated client and a generated (+handwritten) server for e2e test.
But here I first want to see if I can at least pack the tsp files, so each client can get the lib, generate the code from them, compile/lint the code, as a simpler verification.
Let me know your opinon.
github-merge-queue bot
pushed a commit
that referenced
this pull request
May 13, 2025
…atch 0.4.2 (#7145) fix Azure/autorest.java#3110 tsp source from PR #6981 example POM ``` <project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>io.clientcore</groupId> <artifactId>tsptest-builtin</artifactId> <version>1.0.0-beta.1</version> <packaging>jar</packaging> <name>SDK for Builtin</name> <description>This package contains Builtin client library.</description> <url>https://github.com/Azure/azure-sdk-for-java</url> <licenses> <license> <name>The MIT License (MIT)</name> <url>http://opensource.org/licenses/MIT</url> <distribution>repo</distribution> </license> </licenses> <scm> <url>https://github.com/Azure/azure-sdk-for-java</url> <connection>scm:git:git@github.com:Azure/azure-sdk-for-java.git</connection> <developerConnection>scm:git:git@github.com:Azure/azure-sdk-for-java.git</developerConnection> <tag>HEAD</tag> </scm> <developers> <developer> <id>microsoft</id> <name>Microsoft</name> </developer> </developers> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> <dependencies> <dependency> <groupId>io.clientcore</groupId> <artifactId>core</artifactId> <version>1.0.0-beta.9</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.13.0</version> <configuration> <release>11</release> </configuration> </plugin> </plugins> </build> </project> ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #5927
Currently I only add the tsp, not the mockapi.
We can either use service/client added to emitter for the e2e test, or we can still do mockapi (for client emitter; and "knock" for server emitter).
Welcome feedback.