Medic/ Automated testing

[David Kemp <dr...@google.com>]

I have assembled an outline document for the testing platform.
Please review and comment if you are interesting in the automated testing
effort.


https://docs.google.com/document/d/1GMKzZB0DEE0tueeCgbP-rxqfL6uTzZBTmgbBCQ1bdDM/edit?usp=sharing

David Kemp

Re: Medic/ Automated testing

[Andrew Grieve <ag...@chromium.org>]

Could also inject a post-prepare hook to get in there. I think it'd be even
better though, to just figure out how to not need to do the "hack a little
bit" part.


On Mon, Aug 12, 2013 at 5:06 PM, Filip Maj <fi...@adobe.com> wrote:

>
> >Generally true. There are a few bits in the device deployment part that
> >need code that is not part of cli and probably don't make sense to be
> >there. There are some bits that probably should be handled by extensions
> >to
> >cli since there are other reasonable workflows that could use them.
> >
> >For example - Currently cli does not offer a build-deploy only option,
> >which is a problem.  For the current method to work, we need to prepare -
> >hack a little - build & deploy. All of the cli options do a prepare first.
> >So for my first tests I have called the lib scripts directly for that too.
> >I think adding deploy-only to cli makes sense.
>
> We don't offer a deploy-only api through cordova-cli, but we do offer a
> `compile` command: this is a build without a prepare. I am not sure
> whether it is worth exposing this stuff in cordova-cli, or if keeping it
> to the project/cordova/lib scripts is sufficient. I think at this point,
> keeping them under lib/ is good enough. If people really need it, they can
> call into the lib/ scripts by going through ~userdir/.cordova/lib/android
> manually and invoking scripts that way.
>
> >
> >I am less sure that deploying to multiple devices has a target audience
> >other than automated testing...
>
> In general I've always been surprised by what users will do if you provide
> them with the capabilities.. :)
>
>

Re: Medic/ Automated testing

[Filip Maj <fi...@adobe.com>]

>Generally true. There are a few bits in the device deployment part that
>need code that is not part of cli and probably don't make sense to be
>there. There are some bits that probably should be handled by extensions
>to
>cli since there are other reasonable workflows that could use them.
>
>For example - Currently cli does not offer a build-deploy only option,
>which is a problem.  For the current method to work, we need to prepare -
>hack a little - build & deploy. All of the cli options do a prepare first.
>So for my first tests I have called the lib scripts directly for that too.
>I think adding deploy-only to cli makes sense.

We don't offer a deploy-only api through cordova-cli, but we do offer a
`compile` command: this is a build without a prepare. I am not sure
whether it is worth exposing this stuff in cordova-cli, or if keeping it
to the project/cordova/lib scripts is sufficient. I think at this point,
keeping them under lib/ is good enough. If people really need it, they can
call into the lib/ scripts by going through ~userdir/.cordova/lib/android
manually and invoking scripts that way.

>
>I am less sure that deploying to multiple devices has a target audience
>other than automated testing...

In general I've always been surprised by what users will do if you provide
them with the capabilities.. :)

Re: Medic/ Automated testing

[David Kemp <dr...@google.com>]

Generally true. There are a few bits in the device deployment part that
need code that is not part of cli and probably don't make sense to be
there. There are some bits that probably should be handled by extensions to
cli since there are other reasonable workflows that could use them.

For example - Currently cli does not offer a build-deploy only option,
which is a problem.  For the current method to work, we need to prepare -
hack a little - build & deploy. All of the cli options do a prepare first.
So for my first tests I have called the lib scripts directly for that too.
I think adding deploy-only to cli makes sense.

I am less sure that deploying to multiple devices has a target audience
other than automated testing...



On Mon, Aug 12, 2013 at 4:06 PM, Filip Maj <fi...@adobe.com> wrote:

> Looks good! I'm curious to see if either of cordova-cli's apis are
> sufficient to do multi-device discovery / deployment necessary for this
> effort. My feeling is no, and that we'll have to use the
> project/cordova/lib scripts (such as list-devices, install-device, etc) to
> do some of that work.
>
> On 8/12/13 11:29 AM, "David Kemp" <dr...@google.com> wrote:
>
> >I have assembled an outline document for the testing platform.
> >Please review and comment if you are interesting in the automated testing
> >effort.
> >
> >
> >
> https://docs.google.com/document/d/1GMKzZB0DEE0tueeCgbP-rxqfL6uTzZBTmgbBCQ
> >1bdDM/edit?usp=sharing
> >
> >David Kemp
>
>

Re: Medic/ Automated testing

[Filip Maj <fi...@adobe.com>]

Looks good! I'm curious to see if either of cordova-cli's apis are
sufficient to do multi-device discovery / deployment necessary for this
effort. My feeling is no, and that we'll have to use the
project/cordova/lib scripts (such as list-devices, install-device, etc) to
do some of that work.

On 8/12/13 11:29 AM, "David Kemp" <dr...@google.com> wrote:

>I have assembled an outline document for the testing platform.
>Please review and comment if you are interesting in the automated testing
>effort.
>
>
>https://docs.google.com/document/d/1GMKzZB0DEE0tueeCgbP-rxqfL6uTzZBTmgbBCQ
>1bdDM/edit?usp=sharing
>
>David Kemp