Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • +1 for your attempt. But these tools don't work for Android, as I see. Commented Feb 3, 2012 at 20:13
  • @Gangnus Drat, I was hoping at least one would. I'm not familiar with Android-specific development, unfortunately Commented Feb 3, 2012 at 20:42
  • Alas, I have a really hard problem - my app is being debugged not on the emulator, that is in a PC, but on the external Andoid device. So, I am almost sure there is no ready tool for testing it. I should organize the process myself. But how... What have I to check, what are the problems of making such testing, how the regressive test are organized... Everybody gives me links to tools, but I need links to thoughts. Of course, i would take a tool very gladly, but there isn't one... What a sad world... :-) Commented Feb 3, 2012 at 21:11
  • @Gangnus My coworker informs me that even the emulator makes life difficult for debugging the GUI unless you have something designed for it, since it's a whole extra layer to deal with. As for modelling the tests, we use a tool to create flowcharts outlining the path through the program; our tool I think is made in-house, but it has the ability to generate lists of all possible traversals of the flowchart (which become our test scripts), which sounds like a feature you ought to be able to find easily enough or do yourself Commented Feb 3, 2012 at 21:35