Compatibility Test Suite

[Chew Esmero]

Hi,

Anyone who can give us more information about Android Compatibility
Test Suite? There are some blogs that mentioned that you need to be a
device manufacturer to gain access to CTS. That means this CTS can't
be just downloaded freely anytime. Any information regarding this?

I'm not sure this is the correct mailing list to ask this question.
Thanks.

Chew

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

[Vinay H]

check its available in eclair 2.1 R1.

[Uander]

Hello chew , 

follow these steps for cts : 

Step to reproduce:
1. Download Android source code
2. Create a branch based on tag android-2.1_r2
3. Use the following command to generate CTS package:

   . build/envsetup.sh; lunch 1; make cts
4. Unzip the cts package generate at step 3, config SDK_ROOT in startcts
script properly
5. Connect to your device / emulator .
6. Run the following command:
   ./startcts

   start --plan Signature -t android.tests.sigtest.SignatureTest#signatureTest 

will start Signatire test cts plan on cts console .


- Uander

[XC He]

For the generated CTS package, do you mean the "android-cts.zip" ?

2010/4/20 Uander <uand...@gmail.com>:

[Chew Esmero]

Thank you very much. I'll try this one.
But I guess this is for application testing only, am I right?
For device manufacturers, there is a separate CTS that only
Google and the partner are knowledgeable of, right?

Thanks for the info by the way.

Chew

On Apr 20, 1:02 pm, Uander <uandro...@gmail.com> wrote:
> Hello chew ,
>
> follow these steps for cts :
>
> Step to reproduce:
> 1. Download Android source code
> 2. Create a branch based on tag android-2.1_r2
> 3. Use the following command to generate CTS package:
>    . build/envsetup.sh; lunch 1; make cts
> 4. Unzip the cts package generate at step 3, config SDK_ROOT in startcts
> script properly
> 5. Connect to your device / emulator .
> 6. Run the following command:
>    ./startcts
>    start --plan Signature -t android.tests.sigtest.SignatureTest#signatureTest
>
> will start Signatire test cts plan on cts console .
>
> - Uander
>
>
>
>
>
> On Tue, Apr 20, 2010 at 10:22 AM, Vinay H <vinc...@gmail.com> wrote:
> > check its available in eclair 2.1 R1.
>

> > On Tue, Apr 20, 2010 at 8:37 AM, Chew Esmero <chew.esm...@gmail.com>wrote:
>
> >> Hi,
>
> >> Anyone who can give us more information about Android Compatibility
> >> Test Suite? There are some blogs that mentioned that you need to be a
> >> device manufacturer to gain access to CTS. That means this CTS can't
> >> be just downloaded freely anytime. Any information regarding this?
>
> >> I'm not sure this is the correct mailing list to ask this question.
> >> Thanks.
>
> >> Chew
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "android-platform" group.
> >> To post to this group, send email to android-...@googlegroups.com.
> >> To unsubscribe from this group, send email to

> >> android-platfo...@googlegroups.com<android-platform%2Bunsubscrib e...@googlegroups.com>
> >> .

> >> For more options, visit this group at
> >>http://groups.google.com/group/android-platform?hl=en.
>
> >  --
> > You received this message because you are subscribed to the Google Groups
> > "android-platform" group.
> > To post to this group, send email to android-...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > android-platfo...@googlegroups.com<android-platform%2Bunsubscrib e...@googlegroups.com>
> > .

> > For more options, visit this group at
> >http://groups.google.com/group/android-platform?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to android-platfo...@googlegroups.com.

> For more options, visit this group athttp://groups.google.com/group/android-platform?hl=en.

[Christopher Tate]

On Tue, Apr 20, 2010 at 9:36 PM, Chew Esmero <chew....@gmail.com> wrote:
> Thank you very much. I'll try this one.
> But I guess this is for application testing only, am I right?
> For device manufacturers, there is a separate CTS that only
> Google and the partner are knowledgeable of, right?

No, there is only one CTS -- which is now in open-source -- and it is
used only for product compatibility testing, not for application-level
testing. Application level compatibility is managed through adherence
to the published SDKs.

--
chris tate
android framework engineer

[lvsei]

Hi Christopher Tate,

Would you please solve some questions that has bothered me so long
time.

1.There are 8 plans in current Android CTS. Can you tell me what's the
meaning of each plan. For example, which aspect will Android plan test
for?

2.There are 55 packages available when I input the command : ls -p.
But if I input ls --plan Android (and the same for each of the rest
plan), the number of package is shown below:
Android : 28 packages.
Java : 20 packages.
AppSecurity : 1 packages.
CTS : 50 packages.
Performance : 5 packages.
VM : 1 packages.
RefApp : 1 packages.
Signature : 1 packages.

So there are totally 107 plans. Is the 52 packages unavailable???
Why???

3.So far I test my target device plan by plan. But it need to test all
tests in one plan. If I want to test only one test in a plan, I know
there is an example like below:

start --plan Signature -t
android.tests.sigtest.SignatureTest#signatureTest

How can I know other command to test a single test.


Best Regard,
lvsei

On 4月22日, 上午2時43分, Christopher Tate <ct...@google.com> wrote:

> On Tue, Apr 20, 2010 at 9:36 PM, Chew Esmero <chew.esm...@gmail.com> wrote:
> > Thank you very much. I'll try this one.
> > But I guess this is for application testing only, am I right?

> > For device manufacturers, there is a separateCTSthat only

> > Google and the partner are knowledgeable of, right?
>

> No, there is only oneCTS-- which is now in open-source -- and it is

> used only for product compatibility testing, not for application-level
> testing.  Application level compatibility is managed through adherence
> to the published SDKs.
>
> --
> chris tate
> android framework engineer
>
>
>
> > On Apr 20, 1:02 pm, Uander <uandro...@gmail.com> wrote:
> >> Hello chew ,
>
> >> follow these steps forcts:
>
> >> Step to reproduce:
> >> 1. Download Android source code
> >> 2. Create a branch based on tag android-2.1_r2
> >> 3. Use the following command to generateCTSpackage:
> >>    . build/envsetup.sh; lunch 1; makects

> >> 4. Unzip thectspackage generate at step 3, config SDK_ROOT in startcts

> >> script properly
> >> 5. Connect to your device / emulator .
> >> 6. Run the following command:
> >>    ./startcts
> >>    start --plan Signature -t android.tests.sigtest.SignatureTest#signatureTest
>

> >> will start Signatire testctsplan onctsconsole .

>
> >> - Uander
>
> >> On Tue, Apr 20, 2010 at 10:22 AM, Vinay H <vinc...@gmail.com> wrote:
> >> > check its available in eclair 2.1 R1.
>
> >> > On Tue, Apr 20, 2010 at 8:37 AM, Chew Esmero <chew.esm...@gmail.com>wrote:
>
> >> >> Hi,
>
> >> >> Anyone who can give us more information about Android Compatibility
> >> >> Test Suite? There are some blogs that mentioned that you need to be a

> >> >> device manufacturer to gain access toCTS. That means thisCTScan't