Skip to content

chore: Remove 'Run instrumentation tests' section from Contribution Guide #3172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mattcreaser merged 2 commits into from
Jan 5, 2026
+0 −32
Merged

chore: Remove 'Run instrumentation tests' section from Contribution Guide #3172

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5fb9624
Remove 'Run instrumentation tests' section from Contribution Guide
jvh-aws Jan 2, 2026
4b62c94
Merge branch 'main' into jv/remove-run-instrumentation-tests-section-…
jvh-aws Jan 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 0 additions & 32 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,6 @@ contribution.
- [Workflows](#workflows)
- [Adding Code to Support a New Feature](#adding-code-to-support-a-new-feature)
- [Build and Validate Your Work](#build-and-validate-your-work)
- [Run Instrumentation Tests](#run-instrumentation-tests)
- [Test changes to CodeBuild build definitions](#test-changes-to-codebuild-build-definitions)
- [Reporting Bugs/Feature Requests](#reporting-bugsfeature-requests)
- [Contributing via Pull Requests](#contributing-via-pull-requests)
Expand Down Expand Up @@ -319,37 +318,6 @@ Tip: Checkstyle specifies a specific ordering and spacing of import statements,
To setup the Android Studio editor to automatically organize import according to the project checkstyle, go to
Preferences > Editor > Code Style > Java. Under Scheme, select "Project".

### Run Instrumentation Tests

The instrumentation tests presume the presence of various backend resources.
Currently, there is no mechanism for contributors to easily allocate
these resources. This is tracked in [Amplify issue 301](https://github.com/aws-amplify/amplify-android/issues/301).

AWS maintainers can gain access to `awsconfiguration.json` and
`amplifyconfiguration.json` files in an S3 bucket, to find
configurations suitable for running the integration tests.

If you are part of the private access list, the command below will copy
those configurations to your local workspace:

```shell
cd amplify-android
.circleci/copy-configs
```

To run a __specific__ test:

```shell
test='com.amplifyframework.api.aws.RestApiInstrumentationTest#getRequestWithIAM'
./gradlew cAT -Pandroid.testInstrumentationRunnerArguments.class="$test"
```

To run __all__ tests:

```shell
./gradlew cAT
```

### Test changes to CodeBuild build definitions

Changes made to one of the buildspec files under the `./scripts` folder can be tested locally inside a docker container (See [setup instructions](https://docs.aws.amazon.com/codebuild/latest/userguide/use-codebuild-agent.html) in the CodeBuild docs).
Expand Down
Loading