Unlike rake test, m doesn't run pending database migrations before running tests #23

colinyoung opened this Issue Nov 16, 2012 · 2 comments


None yet

2 participants


No description provided.

qrush commented Dec 28, 2012

I don't see how we'd fix this problem easily. I guess you have to remember to run it? M is meant to just be a test runner and not worry about Rails specific things. Going to close this unless if there's better ideas here. I guess there could be a m-rails plugin but I'm not interested in writing or maintaining one.

@qrush qrush closed this Dec 28, 2012

That's a good point. Not sure why I thought this should be an m thing.

EDIT: Actually, I remember now. I hadn't read the m code, but I was under the impression that it used rake test to run some tests, so I wondered why parts of the rake task (e.g. running migrations) weren't running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment