Bugzilla – Bug 15345
Pandora: Pandora needs a beta-pointed build to test important features
Last modified: 2010-02-04 16:20:40 UTC
Pandora needs a beta-pointed build to test important features. There are certain things that can only be tested in the Pandora beta environment. Including: - Thumbs down/fetch new playlist behavior - Device response for invalid audio URLs - Audio ad support - IP licensing restrictions - Read only mode behavior - Auth token timeout behavior
Andy, Pandora says you used to be able to do this easily using some kind of credential info from Pandora. Does it ring any bells? Is there an alternate way of doing this without using your valuable time?
This backend stuff has not changed in a long time so because you already validated it for Radio, Boom, etc, there's not really any need to re-test it for Touch. Pandora is not actually implemented on the device itself, so re-testing this for each product is mostly a waste of time. Other than the different Now Playing screen, Pandora is going to be exactly the same on Radio as on Touch. We could point to beta, but it would screw up every user using 7.5 and test.mysb.com.
Can we get an update on whether this is necessary or not?
Sorry, I thought your first comment indicated that you were not able to do it, so I did not pursue the issue. I think it's necessary moving forward to have a simpler means of testing on beta. Testing on live production data generally isn't allowed for new devices. Even if the platforms are the same or similar, any new device requires the same certification procedures. This is the same policy we have for all device manufacturers. That being said, if it is too difficult or invasive with your environment in it's current state and timeframe, we can probably slide on it for this device, given the certification history of the platform.