Lineman run/spec doesn't always reload correctly when changing git branches.

linemanjs / lineman

Lineman helps you build fat-client JavaScript apps. It produces happiness by building assets, mocking servers, running specs on every file change

MIT License

1.18k stars 80 forks source link

Lineman run/spec doesn't always reload correctly when changing git branches. #213

Closed tandrewnichols closed 9 years ago

tandrewnichols commented 10 years ago

I often find that when I'm working in a branch (with passing tests and a clean index) and then switch back to master, the tests start failing because it's still trying to run specs for code that's not in that branch. I have to restart lineman and rerun the specs to make them green.

searls commented 10 years ago

Huh. How big of a divergence between branches? Config changes? Just source and spec files?

On Thu, Feb 20, 2014 at 10:34 AM, Andrew Nichols notifications@github.com wrote:

I often find that when I'm working in a branch (with passing tests and a clean index) and then switch back to master, the tests start failing because it's still trying to run specs for code that's not in that branch. I have to restart lineman and rerun the specs to make them green.

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/213

tandrewnichols commented 10 years ago

Yeah, usually it's changes to angular controllers/services and their corresponding tests. Often (maybe always - haven't observed real closely) it's with new files that don't exist in master. It's like lineman is holding a reference to the spec and trying to test files that are no longer there.

searls commented 10 years ago

Try hitting enter in testem to force a re-run?

On Thu, Feb 20, 2014 at 11:07 AM, Andrew Nichols notifications@github.com wrote:

Yeah, usually it's changes to angular controllers/services and their corresponding tests. Often (maybe always - haven't observed real closely) it's with new files that don't exist in master. It's like lineman is holding a reference to the spec and trying to test files that are no longer there.

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/213#issuecomment-35637298

tandrewnichols commented 10 years ago

Quitting testem ("q") and rerunning it doesn't usually work (again, I can't recall if this is always or just usually). I have to restart lineman too. This could be a version thing. As we observed when you were here last, our lineman version is super old now (0.16.0 I think).

searls commented 10 years ago

Ah. Latest lineman or it didn't happen. ;-)

On Thu, Feb 20, 2014 at 11:10 AM, Andrew Nichols notifications@github.com wrote:

Quitting testem ("q") and rerunning it doesn't usually work (again, I can't recall if this is always or just usually). I have to restart lineman too. This could be a version thing. As we observed when you were here last, our lineman version is super old now (0.16.0 I think).

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman/issues/213#issuecomment-35637715

tandrewnichols commented 10 years ago

Good motivation to upgrade I guess :)

tandrewnichols commented 10 years ago

This works fine (with the latest lineman) unless your current branch has new node_module dependencies that old code doesn't (I think).

linemanjs / lineman

Lineman run/spec doesn't always reload correctly when changing git branches. #213

I often find that when I'm working in a branch (with passing tests and a clean index) and then switch back to master, the tests start failing because it's still trying to run specs for code that's not in that branch. I have to restart lineman and rerun the specs to make them green.

Yeah, usually it's changes to angular controllers/services and their corresponding tests. Often (maybe always - haven't observed real closely) it's with new files that don't exist in master. It's like lineman is holding a reference to the spec and trying to test files that are no longer there.

Quitting testem ("q") and rerunning it doesn't usually work (again, I can't recall if this is always or just usually). I have to restart lineman too. This could be a version thing. As we observed when you were here last, our lineman version is super old now (0.16.0 I think).