Isolate ModuleStore Signals During Tests

Description

The Platform team is investigating the feasibility of mocking the modulestore interface with the goal of saving time on unit test runs:

https://openedx.atlassian.net/wiki/display/PLAT/Moving+modulestore+investigation
https://openedx.atlassian.net/wiki/display/PLAT/Mocking+modulestore+-+optimal+seam+investigation

A good portion of the time spent in tests actually comes from the events that trigger off of course publish signals, rather than the modulestore operations themselves. Removing these (or only selectively turning these on where needed) will reduce test run time significantly. This will also help make tests more predictable, so that adding a new publish listener won't break a bunch of query counting tests. It's similar in principle to what we already have in place for cache isolation.

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Assignee

David Ormsbee

Reporter

David Ormsbee

Labels

None

Reach

None

Impact

None

Platform Area

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Story Points

3

Sprint

None

Priority

Unset
Configure