Hi Mark - possibly a quick one. Do you have any pointers for doing TDD/BDD on Android?

hello, ramsey!

I don't have any particular sites to point you towards, if that is what you mean

OK when you're making an app, say - do you follow the TDD principles or just go straight in and test later?

speaking personally, it depends entirely on what I am writing

on the whole, I'm not much of a TDD guy

TDD isn't bad; it's just not the way my mind works

OK that's v interesting. So it's definitely not a must then?

the only time TDD is a "must" is if a development team or manager has decided it is a "must"

otherwise, it is just a development technique, nothing more

again, TDD is not a bad idea, though I do find that how easy it is to do TDD depends on development language and frameworks (e.g., TDD on Ruby is easier than TDD on Android/Java)

OK that's useful thanks. So do you do your testing after you've built the features? It's useful that you say it's harder on Android - because that's been my experience but wasn't sure how to get around it!

again, it depends upon what I am writing

And do you spend lots of time writing unit tests etc? Or is it more informal?

I would not say that I am particularly representative of how Android development is done in general

I am one guy, working independently, mostly writing book examples

Yeah - I suppose it's a less specific question. But it's useful to know how other Android devs do it

the testing requirements for that are low

True. Perhaps I need to get onto some android forums

But that's been helpful Mark. Just the insight - thanks

for larger stuff, I typically write a bunch of production code, to get a core established, before getting serious about automated testing

if you have another question, go right ahead -- it's a quiet chat room this morning

hi

hello, MyWay!

how can I help you today>

er, today?

I've received this trace... http://pastebin.com/1JEiFucJ it's from a single device

but I can't understand what can be the reason

I can't see any of my classes inside it

how can I investigate what's happening?

well, the line numbers don't quite line up with the current ViewPager source code

try to track down the source code for the version of ViewPager that you are using, then see what line 1605 is

a quick skim of the current ViewPager code isn't turning up much that might trigger a local NPE in onLayout()

a child with a null LayoutParams would, though I don't know how you would wind up with that, since we don't add children to ViewPager directly ourselves

if (child.getVisibility() != GONE) {

this is the viewpager line

that would imply that getChildAt() for a valid index returned null

and I have no idea how that would happen

I have no idea too, I'm neither able to reproduce it

unless it starts happening with some frequency, I wouldn't worry about it too much

for all you know, a cosmic ray flipped a bit somewhere

eheh

cosmic rays are sneaky that way

yes

maybe something specific to samsung GT-I9060I's ROM?

that's not completely out of the question

some Samsung 4.2 devices were caught baking in a copy of appcompat-v7

wasn't a big problem, until the v21 appcompat-v7, with all the Material backport stuff, came in

ah

the firmware always wins, and so classes in the firmware trumped those in the library

which broke a bunch of apps

it's conceivable that they baked in support-v4 as well

not a whole lot you can do about that

yes, thank you

Have a good day to all, bye Mark and thank you

you are very welcome

that wraps today's chat

the transcript will be posted to https://commonsware.com/office-hours/ shortly

the next chat is tomorrow at 7:30pm US Eastern time

have a pleasant day!