Use users.tests.get_user() instead of hard-coding 118533. It just so happens that get_user() is specced to return that exact user.
This is easy pickins. Might as well do it now before we copy-and-paste all that code over and over again and make the code sillier.
Whiteboard: u=user c=search s=2012.1 p=
Whiteboard: u=user c=search s=2012.1 p= → u=user c=search s=2012.1 p=1
Grabbing this before we do more ES tests.
Assignee: nobody → willkg
ES tests use model makers now, so this is m00t. Marking as WONTFIX since there's nothing to do here.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
I missed the app-specific ES tests. This is still a problem with questions/tests/test_es.py and forums/test/test_es.py. Reopening.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Grabbing after talking to Will. I needed this to happen so I could kill the mixins and fixtures in the ES tests.
Assignee: willkg → erik
...which I need to happen so I can write decent tests for bug 710469.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago → 7 years ago
Resolution: --- → FIXED
Pretty sure this lands in 2012-01-17.
Target Milestone: --- → 2012-01-17
Whiteboard: u=user c=search s=2012.1 p=1 → u=dev c=search s=2012.1 p=1
Please add QA verification steps, or mark as [qa-], thanks
The tests verify this sufficiently. (Let see if the sprint graphs trip over this.)
Whiteboard: u=dev c=search s=2012.1 p=1 → u=dev c=search s=2012.1 p=1 [qa-]
Closed as [qa-]
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.