As Keunyoung noted we are working on continuing to optimize the tests, improve documentation and provide alternate test tools. We will share this as soon as possible, in the interim please note that this is code that has not been fully validated.
On Monday, April 15, 2013 7:08:53 PM UTC-7, Pedro Sardon wrote: > > Hi George, > > I am not sure, actually we also run the normal test cases (ignoring the > error in the environment test case) > > seems most of the test cases can pass. so I am not sure how related > is MixerTest.tryTinyAlsaTest with the other test cases. > > I have also traced the code and seems the tinyalsatest verifies the number > of mixers in the M-Audio Mobile. the test case requires 0 mixers. > which doesn't makes to much sense to me. > > If you have any other update about it please help to post it here. > > Cheers, > Pedro > > On Friday, April 12, 2013 11:27:11 AM UTC+8, Lin George wrote: >> >> >> >> Hi Pedro. >> >> The same situation the same with you in my case. >> >> We can pass all test items besides MixerTest.tryTinyAlsaTest in >> environment test. >> >> But it seems not affect normal test case since tinyalsa test fail, >> does it mean anything if we can't pass tinyalsa test? >> >> >> Thanks >> >> George >> >> >> On Thursday, March 28, 2013 10:53:42 AM UTC+8, Pedro Sardon wrote: >> >>> Hi Stan, >>> >>> We got the same CTS-Audio Quality Verifier from Android (beta version) >>> and I run it with JB 4.1.1, >>> >>> Seems there is an error in the test case: >>> MixerTest.tryTinyAlsaTest >>> That is the only test case we can't pass, (at least in the Setting up >>> Hardware part) it seems an specific M-Audio Mobile Pre USB audio device is >>> required but Google has not given any specification about it. >>> >>> could you post some detail about your fail items? >>> >>> Regards, >>> Pedro. >>> >>> On Tuesday, March 5, 2013 5:37:07 PM UTC+8, huang stan wrote: >>>> >>>> Hi, Android guys: >>>> >>>> Could you please help to comment this question ? :) >>>> >>>> We got the "beta" version of CTS- Audio Quality Verifier from Android >>>> guys in the end of December (last year). >>>> (It is the beta version that you don't release.) >>>> >>>> We test it on JellyBean 4.2. But we can't pass all the test items. >>>> Seem that the environment is not set up well. (for M-Audio Mobile Pre >>>> USB audio device) >>>> So we need you to give some suggestions. :) >>>> >>>> Thanks >>>> >>>> BRs, >>>> Stan >>>> >>>> >>>> Lin George於 2013年2月21日星期四UTC+8下午3時46分52秒寫道： >>>>> >>>>> Dear all, >>>>> >>>>> I am trying to do CTS - Audio quality verifier in JB4.1.2 and >>>>> JB4.2.3 >>>>> >>>>> According to the spec definition , I got to buy M-Audio Mobile >>>>> Pre USB audio device. >>>>> >>>>> But I try to replace M-Audio Mobile Pre with Creative USB Sound >>>>> Blaster, is it workable? >>>>> >>>>> Following and attachment is the test result when running >>>>> cts_audio_quality_test >>>>> >>>>> Must I buy M-Audio Mobile Pre USB audio device for CTS Audio >>>>> verifier test? >>>>> >>>>> Thanks >>>>> George >>>>> >>>>> >>>>> >>>>> [----------] Global test environment tear-down >>>>> [==========] 61 tests from 20 test cases ran. (51063 ms total) >>>>> [ PASSED ] 51 tests. >>>>> [ FAILED ] 10 tests, listed below: >>>>> [ FAILED ] SignalProcessingInterfaceTest.InitTest >>>>> [ FAILED ] SignalProcessingInterfaceTest.EchoTest >>>>> [ FAILED ] SignalProcessingInterfaceTest.intsumTest >>>>> [ FAILED ] SignalProcessingInterfaceTest.TwoInstanceTest >>>>> [ FAILED ] SignalProcessingInterfaceTest.exampleTest >>>>> [ FAILED ] MixerTest.tryTinyAlsaTest >>>>> [ FAILED ] ClientInterfaceTest.getDeviceInfoTest >>>>> [ FAILED ] ClientInterfaceTest.PlayTest >>>>> [ FAILED ] ClientInterfaceTest.RecordTest >>>>> [ FAILED ] ScriptExecTest.PythonVersionTest >>>>> >>>>> 10 FAILED TESTS >>>>> >>>>> >>>> -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
