Closed Bug 974912 Opened 11 years ago Closed 11 years ago

[dev] Only one Submission ID per app in Content Ratings

Categories

(Marketplace Graveyard :: Developer Pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: AndreiH, Unassigned)

Details

(Whiteboard: [missing_functionality])

We currently were using 'Subm-381' as a submission ID in our tests when submitting an app. We are now blocked because it seems that thinks have changed and we only can use one submission ID per app. I guess we cannot automate to generate an new ID every single time the tests run. How to you guys suggest to test this? Here is a screencast: http://screencast.com/t/gsHufjXDF Note: We currently do not have any submitted apps, the one in the video was the first one.
Andrei, You can see the new behavior here : https://bugzilla.mozilla.org/show_bug.cgi?id=972437 Based on comment #3, I think that you can solve your problem by deleting your submission at the end , so you will be able to use same ID for the next test involving new app submission.
We have other tests that run on those previously submitted apps. If we delete the apps after submission the next running tests won't have apps to run on. We have to rethink how our tests runs
I know this doesn't help in the very short term, but I have been working on getting the Marketplace API working for creating apps. Once that is working reliably, we should be able to create, and then delete an app for each test, which I think (based on what Victor said) will resolve this issue. I'm not sure what we can do in the short term though.
AndreiH, Let's create a unique submission ID as part of the submission process. That would fix the issue.
AndreiH, On second thoughts, let's have this check disabled on dev and stage. So, you should be able to use the same ID across apps. See https://bugzilla.mozilla.org/show_bug.cgi?id=975050 for more details. I'll close this bug since the other bug takes care of your issue.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [missing_functionality]
You need to log in before you can comment on or make changes to this bug.