On 01/04/15 13:58, Jonathan Aquilina wrote: > > > I couldn't agree more, I am not an E developer, but would eventually > like to become one. Unit testing not only for the new API features, but > for any feature of E unit tests should be applied. I think if someone > comes up with a use case even if its a corner case a test case should be > written for it. >
Yes, that's what we talked about at dev day. We aspire to have 100% coverage, at least for things that can be feasibly tested. With exactness, we plan to also have high coverage with pixel perfect regression tests. We plan on having full code coverage in both. However, it's going to be a losing battle if for every line we cover, 3 more we don't are going to be added. It's like we've done with warnings. It was annoying to fix them until we added the no new warnings rule. -- Tom. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
