@@ -17,7 +17,6 @@ contribution.
1717 - [ Workflows] ( #workflows )
1818 - [ Adding Code to Support a New Feature] ( #adding-code-to-support-a-new-feature )
1919 - [ Build and Validate Your Work] ( #build-and-validate-your-work )
20- - [ Run Instrumentation Tests] ( #run-instrumentation-tests )
2120 - [ Test changes to CodeBuild build definitions] ( #test-changes-to-codebuild-build-definitions )
2221 - [ Reporting Bugs/Feature Requests] ( #reporting-bugsfeature-requests )
2322 - [ Contributing via Pull Requests] ( #contributing-via-pull-requests )
@@ -319,37 +318,6 @@ Tip: Checkstyle specifies a specific ordering and spacing of import statements,
319318To setup the Android Studio editor to automatically organize import according to the project checkstyle, go to
320319Preferences > Editor > Code Style > Java. Under Scheme, select "Project".
321320
322- ### Run Instrumentation Tests
323-
324- The instrumentation tests presume the presence of various backend resources.
325- Currently, there is no mechanism for contributors to easily allocate
326- these resources. This is tracked in [ Amplify issue 301] ( https://github.com/aws-amplify/amplify-android/issues/301 ) .
327-
328- AWS maintainers can gain access to ` awsconfiguration.json ` and
329- ` amplifyconfiguration.json ` files in an S3 bucket, to find
330- configurations suitable for running the integration tests.
331-
332- If you are part of the private access list, the command below will copy
333- those configurations to your local workspace:
334-
335- ``` shell
336- cd amplify-android
337- .circleci/copy-configs
338- ```
339-
340- To run a __ specific__ test:
341-
342- ``` shell
343- test=' com.amplifyframework.api.aws.RestApiInstrumentationTest#getRequestWithIAM'
344- ./gradlew cAT -Pandroid.testInstrumentationRunnerArguments.class=" $test "
345- ```
346-
347- To run __ all__ tests:
348-
349- ``` shell
350- ./gradlew cAT
351- ```
352-
353321### Test changes to CodeBuild build definitions
354322
355323Changes 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).
0 commit comments