Closed
Bug 982415
Opened 11 years ago
Closed 11 years ago
Load test: add tests for generation numbers in assertion and client state string
Categories
(Cloud Services Graveyard :: Server: Token, defect, P1)
Cloud Services Graveyard
Server: Token
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jbonacci, Assigned: rfkelly)
Details
(Whiteboard: [qa+])
This came up in today's meeting.
A bit more work to really fill out the TS load test.
This was https://github.com/mozilla-services/tokenserver/issues/43
|
Reporter | |
Updated•11 years ago
|
Whiteboard: [qa+]
|
|
Reporter | |
Updated•11 years ago
|
Priority: -- → P2
|
|
Reporter | |
Updated•11 years ago
|
Assignee: nobody → rfkelly
Priority: P2 → P1
QA Contact: jbonacci
|
Assignee | |
Comment 1•11 years ago
|
||
I'm going to WONTFIX this because I can't think of a good way to do it without introducing a bunch of errors and corner-cases. E.g. if we *ever* send a non-zero generation number for a user, all subsequent requests for that user will have to use the same or greater generation number. Let's depend on functional tests rather than adding this to the loadtest.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
|
||
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•