Highlights and Insights: NDC 2013 Conference, Day 3
Aka. the day of automated testing.
Sharing C# across Windows, Android and iOS using MvvmCross
MvvmCross makes it easy to implement the MVVM-pattern on iOS, Android, Windows Phone, Mac, Win RT and others, and facilitates code sharing of the ViewModel logic across all the supported platforms. With the help of PCL (Portable Class Libraries), you can achieve code sharing in the upper 80%s of your code base. Even more if you use little custom UI. The view itself cannot be shared, and that is as it should be.
Properly decoupled view models are easy to test and with the code shared across all your platforms, the tests will have high value.
MvvmCross enables cross platform development with native UI and performance, together with easily testable code. I've used MvvmCross myself and highly recommend it to everybody interested in multi-platform development. For an introduction, check out the MvvmCross N+1 video series.
Succeeding with TDD: Pragmatic Techniques for effective mocking
- If your code is not testable, your design sucks. Separation of concerns, dependency inversion and the single responsibility principle helps with both design and testability.
- TDD takes you from unknown to known, one small step at the time.
- Start with your needs and map the world to you.
- Use mocks sparingly and keep them simple! Never make a mock more complex. If you hear "Do we need to write unit tests for the mock?" you have failed in this regard. An example:
I would have stressed more that you don't start with TDD, you start with unit tests. Understanding how to write relevant and well designed tests are a precursor for a successful application of TDD.
His focus was somewhat different from Venkat's previous talk. Rather than starting with C# threading basics, Jon made the case for async and await using metaphors and code examples. As we've previously learned, asynchrony does not equal parallelism.
C# in its current iteration has many different APIs for dealing with asynchrony. Your code will be easier to develop, understand and extend if you stick with one of these paradigms. Switching points between synchronous and asynchronous code can be painful.
Jon stressed the need for giving the user early feedback. For example, show items in a list as they come in. Don't wait for all the items before giving the user the option to work with the data. Also, validate input as early as possible so that exceptions caused by bad input do not happing during the asynchronous operations.
Testing was the last topic:
- Keep tests for plain business logic and asynchronous operations separate.
- Take control of time and consider using an abstraction so that the ordering of execution can be controlled from the tests.
- Test for different permutations of completion order for the different asynchronous tasks. The tests should still pass even if the code is run synchronously.
C# 5 lets you focus on the difficult bits... And that's good!