thanks Daniel, I've decided to go this route. Didn't realize that reading the DOM also counted as 'dom manipulation'...which I know is a bad practice.
On Sunday, January 5, 2014 1:04:59 AM UTC-5, Daniel Tabuenca wrote: > > One of the great things about unit testing is that when you encounter > friction it really is trying to tell you are likely doing something you > shouldn't. You should consider encapsulating whatever action you are doing > on the dom inside of a directive. For example you can have a directive that > writes out whatever property you are testing for into the scope This is not > difficult, and will make things much easier to test. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
