All joking aside - there is a pretty slick alpha / beta release
process in the store for getting your app in the hands of pre-release
testers.
IMO, it kicks the snot out of junk like downloading and running an app
installer, or tools like testflight.
Larry
--
--
You received this message becau
Best way is giving it away to Users to test. That way they will try and
break the Application and give you the appropriate feedback
Thanks.
Ameya
On Thursday, June 27, 2013 12:54:50 PM UTC+1, vani wrote:
>
>
> Dear All,
>
> What is the best and optimistic way to test Android applications,My
>
Best testing strategy ever...and it's not even Friday.
On Thu, Jun 27, 2013 at 6:19 AM, Piren wrote:
> release it to the public :)
>
>
> On Thursday, June 27, 2013 2:54:50 PM UTC+3, vani wrote:
>>
>>
>> Dear All,
>>
>> What is the best and optimistic way to test Android applications,My
>> andro
release it to the public :)
On Thursday, June 27, 2013 2:54:50 PM UTC+3, vani wrote:
>
>
> Dear All,
>
> What is the best and optimistic way to test Android applications,My
> android application is too big.How to find a way to get minute bugs in the
> application.??
> --
> Regards,
> Vani Reddy
Yep, been a while, so busy these days with Android, things a bit crazy. I'm
finding some time finally to start doing open-source again...I think last
time I posted here, I got a bunch of private hate email for something I
said :)
On Thu, May 31, 2012 at 6:20 AM, JP wrote:
>
>
> Shane Isbell is b
Shane Isbell is back; haven't heard in a while!
On May 30, 3:37 pm, Shane Isbell wrote:
> Hi all, I'm starting work on an android integration testing framework,
> called Huntsville:
>
> https://github.com/sisbell/huntsville
>
> Currently, the project creates a DeviceAssert (extending JUnit Ass
The Android test case classes provide a way to *unit-test* a method or
methods that have to run in the Android environment. Since they do unit
tests, you should be able to test your library code within a larger .apk
test harness. One way to do this would be to build a purpose-coded test
harness
well, the problem here is that we have a commons, which is an android
library used across multiple projects,
which are common classes, resources etc which most of them cannot be
tested independently,and from what I can see
it generally means that the projects cannot be tested at all if they
use an
s itried with the same as it is giving permission denied .
is there any restrictions like the user of the system need full
admin permissions to open the adb shell .
On Nov 24, 2:33 am, "A. Elk" wrote:
> I interpret this to mean that you tried to test with the emulator.
> Which commands give yo
I interpret this to mean that you tried to test with the emulator.
Which commands give you "permission denied"?
On Nov 22, 10:57 pm, kampy wrote:
> hi
>
> as u said i read the doc and there i found that i can do these testing
> on the emultor terminal adb shell but for every command i typed it i
Depends on exactly what you mean by "while testing". If you are using
the Android unit testing framework described in
http://developer.android.com/guide/topics/testing/testing_android.html
then the answer is "no". The unit testing framework is for testing a
single class, so you can't test more th
hi
as u said i read the doc and there i found that i can do these testing
on the emultor terminal adb shell but for every command i typed it is
giving the permission denied . how to obtain the permissions for
this ..
On Nov 23, 11:22 am, welly tambunan wrote:
> have u try this one
>
> htt
Can you attach some code snippets from your test app? Are you using
clickView() or tapView()?
You must call setActivityInitialTouchMode(true) before you do a
startActivity(). Seems that you're doing this if you call it in
setUp(), although I could be wrong.
Unfortunately, I'm not familiar with Ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 19:11 , A. Elk wrote:
> In other words, you can do button presses in a "sample" Android
> app from a test package, but you can't do them from your app's
> test package to the app under test.
Right.
> (The test package is the same as the "t
In other words, you can do button presses in a "sample" Android app
from a test package, but you can't do them from your app's test
package to the app under test.
(The test package is the same as the "test app" and the "app under
test" is the application you're trying to build.)
Are you using Acti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 17:56 , Brion Emde wrote:
> Did you try working with the testing tutorial?
>
> http://developer.android.com/resources/tutorials/testing/activity_test.html
>
>
>
That gives an example of using the Instrumentation to send key presses
> to an A
Did you try working with the testing tutorial?
http://developer.android.com/resources/tutorials/testing/activity_test.html
That gives an example of using the Instrumentation to send key presses
to an Activity.
On Aug 5, 10:22 am, Fabrizio Giudici
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> H
Hi,
thanks for the messages.
I have a screen which gets input from the user,
this screen should be called once, but in execution, after inputing
all the data and clicking the continue button the input screen re-
appears. The continue button should and does in the emulator display a
menu screen. I
Add debugging to the life cycle methods, this should help you see
exactly what is going on and at least analyse a time line of events.
On Apr 23, 2:44 pm, HowlettAndroid
wrote:
> Hello,
>
> Hope you lot can help. I'm currently testing my application in
> the SDK emulator, Great everythin
You havnt clearly defined the problem. When is your activities called
again? By called again you mean these activities get restarted?
If I am guessing right this happens when you slide out the keyboard
(when the orientation is changed)?
On Apr 23, 8:44 am, HowlettAndroid
wrote:
> Hello,
>
>
Hi gents
I am running fedora 8 with eclipse and have the sdk and plugin setup.
It work like a champ. I have regular g1 with the debug on and
developed one app sofar and it has worked great with no real issues.
I really liked the live debug option.
Ed
On Mar 10, 5:54 pm, mark.ka...@gmail.com wrot
You do need to enable debugging to use adb, under Settings ->
applications -> development
M
On Mar 10, 2:52 pm, mark.ka...@gmail.com wrote:
> I just use a regular G1 for development, got it before the dev phone
> came out. You can access it with adb as usual. You don't
I just use a regular G1 for development, got it before the dev phone
came out. You can access it with adb as usual. You don't have root
access, but this doesn't seem to matter for developing normal apps,
only if you plan on hacking or setting up your own linux layer code
etc. You also get the a
If you're running Vista you may encounter problems with the USB connection.
Al.
Mike Pastor wrote:
>
> Fellow Developers,
>
> Has anyone experienced problems with using the TMobile G1 (usa) as a
> serious Android testing machine? Is it a seamless task to load the G1
> phone from your developmen
I have connected a G1 to my development laptop and used eclipse just as
I would when using the emulator to automatically deploy apk's and run
and test them, and have the logcat readout looks just as per with the
emulator.
There is at least one difference which I noticed. You do NOT have root
25 matches
Mail list logo
