Take a look at some of the tests we have already. They verify not just the message being output but also the node provided for it. That node is/will be used by reporters to get the relevant source code to display in the console. Making sure the right node is returned is incredibly important for having "evidence" of the problematic code.
On Tue, Oct 8, 2013 at 5:27 PM, Andrew de Andrade <[email protected]>wrote: > On Tue, Oct 8, 2013 at 4:19 PM, Nicholas Zakas <[email protected] > > wrote: > >> I would like to be able to test more than just the outputting error >> message because it's also important that the right node be returned with >> the error message, for example. >> > > Tell me more about this. I'm not sure what you mean and want to keep it in > mind while I work on this. > > -- > You received this message because you are subscribed to the Google Groups > "ESLint" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- ______________________________ Nicholas C. Zakas @slicknet Author, Professional JavaScript for Web Developers Buy it at Amazon.com: http://www.amazon.com/Professional-JavaScript-Developers-Nicholas-Zakas/dp/1118026691/ref=sr_1_3 -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
