cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dpogue <>
Subject [GitHub] cordova-android pull request #382: CB-12859: document how to run the native ...
Date Thu, 25 May 2017 20:05:24 GMT
Github user dpogue commented on a diff in the pull request:
    --- Diff: test/ ---
    @@ -0,0 +1,58 @@
    +# Licensed to the Apache Software Foundation (ASF) under one
    +# or more contributor license agreements.  See the NOTICE file
    +# distributed with this work for additional information
    +# regarding copyright ownership.  The ASF licenses this file
    +# to you under the Apache License, Version 2.0 (the
    +# "License"); you may not use this file except in compliance
    +# with the License.  You may obtain a copy of the License at
    +# Unless required by applicable law or agreed to in writing,
    +# software distributed under the License is distributed on an
    +#  KIND, either express or implied.  See the License for the
    +# specific language governing permissions and limitations
    +# under the License.
    +# Cordova Android Test Project
    +The project in this directory is an Android Test project that enables those
    +interested in further developing cordova-android to validate their changes.
    +## Requirements
    +The requirements in the top-level README still apply. In addition, ensure you
    +have installed Gradle, and that it is (at the time of this writing) at least
    +version 3.3 or newer.
    +## Getting Started
    +You can run this test project from both the command line as well as from
    +Android Studio.
    +### Command Line
    +Ensure you have the gradle wrapper script, `gradlew`, in this directory. If
    +you do not, you can run the following to generate it:
    +    $ cd cordova-android/test
    +    $ gradle :wrapper -b build.gradle
    +You can then see a list of all tasks available to run with `gradlew tasks`.
    +The two different kinds of tests one typically wants to run are unit tests and
    +end-to-end, or instrumented, tests. Unit tests do not require any particular
    +environment to run int, but the instrumented tests, however, require a
    --- End diff --
    int -> in

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message