Closed Bug 761575 Opened 13 years ago Closed 13 years ago

implement comprehensive tests for elasticsearch unified search view

Categories

(support.mozilla.org :: Search, defect, P1)

Product:
support.mozilla.org
Component:
Search
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2012.12

People

(Reporter: willkg, Assigned: willkg)

References

Details

(Whiteboard: u=dev c=search p=2)

This bug covers: writing tests covering the unified search view
Nixing the block on bug #761573---this doesn't block that, but rather depends on it. Putting this in 2012.11 because it needs to get done. I broke this out as a separate bug, but it can't get shipped by itself as it needs the unified search view code in order for the tests to do stuff. However, I thought it's useful to break this out so that the points for the total project are correct and we get a better feel for our velocity. Making this a 2 pointer. I think I can reuse some of the existing ES tests, but clearly I'll need to write some new ones.
No longer blocks: 761573
Depends on: 761573
Whiteboard: u=dev c=search p=2
Summary: implement elasticsearch unified search view → implement tests for elasticsearch unified search view
Changing the scope of this bug slightly. This bug now covers writing tests for all the filters in the ES unified search view. The outcome of this bug is that we'll have a really solid idea of whether all the things we're doing in search are working correctly for ES search view code. Bumping this to 2012.12 since while I added a few tests when working on the unified search view code, it's not comprehensive.
Summary: implement tests for elasticsearch unified search view → implement comprehensive tests for elasticsearch unified search view
Oops--bumping it to 2012.12 for realz.
Target Milestone: 2012.11 → 2012.12
Landed in master in https://github.com/mozilla/kitsune/commit/e47e5ae21a025b38ffcd921bf18e61c960dce8e3 Pushed to production just now. Not that pushing tests to production is particularly interesting, but so it goes.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.