smithy-rs/codegen-client-test
Russell Cohen a95b8b311b
Disable formatter (#3417)
## Motivation and Context
running codegen tests produces a diff you need to ignore

## Checklist
<!--- If a checkbox below is not applicable, then please DELETE it
rather than leaving it unchecked -->
- [ ] I have updated `CHANGELOG.next.toml` if I made changes to the
smithy-rs codegen or runtime crates
- [ ] I have updated `CHANGELOG.next.toml` if I made changes to the AWS
SDK, generated SDK code, or SDK runtime crates

----

_By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice._
2024-02-19 15:23:11 -05:00
..
model Ignore actual default value instead of 0/false (#3252) 2023-12-15 16:37:36 +00:00
.gitignore Establish the `codegen-core` module (#1697) 2022-09-07 09:31:46 -07:00
README.md Break up `RustCodegenDecorator` (#2099) 2022-12-14 13:26:55 -08:00
build.gradle.kts Disable formatter (#3417) 2024-02-19 15:23:11 -05:00

README.md

Codegen Integration Tests

This module defines integration tests of the code generation machinery. ./build.gradle.kts will generate a smithy-build.json file as part of the build. The rust-client-codegen Smithy build plugin then invokes our codegen machinery and generates Rust crates, one for each of the integration test services defined under model/.

Usage

These commands are all meant to be run from the repository root.

To run all protocol tests of all the integration test services:

./gradlew codegen-client-test:build

To run only a subset of the integration test services (refer to ./build.gradle.kts for a full list):

./gradlew codegen-client-test:build -P modules='simple,rest_json'

The Gradle task will run cargo check, cargo test, cargo docs and cargo clippy by default on all the generated Rust crates. You can also specify a subset of these commands. For instance, if you're working on documentation and want to check that the crates also compile, you can run:

./gradlew codegen-client-test:build -P cargoCommands='check,docs'

For fast development iteration cycles on protocol tests, we recommend you write a codegen unit test with a minimal service definition and only run that unit test. Alternatively, you can write a minimal integration test service definition in model/simple.smithy and run:

./gradlew codegen-client-test:build -P cargoCommands='test' -P modules='simple'