angular 1.2 "Attempted to assign to readonly property"

[Nate Brustein]

Ever since updating to angular 1.2, I keep running into tests that fail with "TypeError: Attempted to assign to readonly property." and no useful stack trace.  I've tracked these down to different issues in different cases.  Some examples:

• cases where I'm accessing a variable that I hadn't declared with "var," 
  
• cases where I had failed to include a template in my test (which in the old angular used to give a really useful error saying exactly which template you had failed to include)
  

I'm wasting a lot of time every day trying to track down these errors.  Without a stack trace or a useful message it's really hard to figure out what's going on.

Are other people having this issue?  Is there some way around it?

Thanks,

Nate

[Nate Brustein]

Update: It seems like the issue is maybe only in PhantomJS.  I started using Chrome for my tests, and I'm getting real stack traces again.

[Nate Brustein]

See https://github.com/karma-runner/karma/issues/831#issuecomment-28797090 for more discussion of this issue