Hello,
I'd like to run this by the forum as I've had a lot of trouble finding ways to come up with good solid testing strategies for location apps on a mobile device.
This may boil down to finding the best mock frameworks, but I'm more interested in the workflow that people use:
What would be the best strategy to mock a discovery service for finding locations and returning results?
One of the main issues I have as a J2ME/BlackBerry developer is the strong reliance on an active simulator running. One way I've thought is to isolate the core code into a domain layer and run it in isolation of the emulator (as a standard J2SE JUnit app). The problem with that is that the infrastruture components are part of the device per se and I'm not sure what the approach would be to get round this.
Any thoughts?
I'd like to run this by the forum as I've had a lot of trouble finding ways to come up with good solid testing strategies for location apps on a mobile device.
This may boil down to finding the best mock frameworks, but I'm more interested in the workflow that people use:
What would be the best strategy to mock a discovery service for finding locations and returning results?
One of the main issues I have as a J2ME/BlackBerry developer is the strong reliance on an active simulator running. One way I've thought is to isolate the core code into a domain layer and run it in isolation of the emulator (as a standard J2SE JUnit app). The problem with that is that the infrastruture components are part of the device per se and I'm not sure what the approach would be to get round this.
Any thoughts?