Conventional compatability testing will give you a list of buggy methods for a particular device.
Now with the awful quality of J2ME API implementations, I have begun to think this is the wrong way around.
It would be easier to list the API methods, and against it list the handsets on which the method is faulty.
For a little fun (and also a little education!), I propose we begin a Thread to achieve this.
One person will state an api method (fully qualified!) ,
and others race to respond with a device on which said method behaves incorrectly. (and how it behaves incorrectly)
The first to respond gets to select the next method! =)
So, what do you all think? =)
If someone is willing to select a method to kick us off?
For the sake of fair-play; lets keep the API set to just the major ones, say :-
midp1, cldc1, midp2, cldc1.1, jsr135, jsr184, samsung, nokia, motorola, siemens, benq(o2x2/midp2 hybrid), sprint, vodafone, jphone, mascot, (any important API’s i’ve forgotten?)