When performing an MsDeploy to an Azure Web App and you have the App Insights extension enabled you may find something interesting happens if you use the option to delete additional files on the destination that don’t appear in the source. If you look at the deployment log you may see something like this:
Just a quick note that the videos for the presentations I delivered with Matt Davies at NDC Sydney 2016 are up:
- Microtesting: How We Set Fire To The Testing Pyramid While Ensuring Confidence
- Modern Authentication
It was an amazing conference to attend, let alone present at and I’m looking forward to this year’s conference!
This morning I presented a talk on modern authentication with Matt Davies to the Yow! West conference.
I just published the slides at https://github.com/MRCollective/ModernAuthPresentation.
I’m somewhat more subdued with my excitement for announcing this than I was for 1.0. In fact I just had a chuckle to myself in re-reading that post :) (oh and if you were wondering - did Matt and I enjoy Borderlands 2? Yes we very much did, it’s a great game).
Nonetheless, there is some really cool stuff in ChameleonForms 2.0 and I’m particularly excited about the new PartialFor functionality, which I will describe below. My peak excitement about PartialFor was months ago when the code was actually written, but Matt and I have had a particularly busy second half of the year with our work roles expanding in scope and a healthy prioritisation of our personal lives so it took a while to get our act together and get the code merged and released.
There have been a range of point releases that added a bunch of functionality to ChameleonForms since the 1.0 release and before this 2.0 release. You can peruse the releases list to see the features.
I recently gave a couple of conference talks:
Do you want to write less tests for the same amount of confidence? Do you want to print out the testing pyramid on a dot matrix printer, take it outside and set fire to it?
How confident are you that you can survive the refactoring apocalypse without breaking your tests?
As consultants, we get to see how testing is performed across many different organisations and we have a chance to experiment with different testing strategies across multiple projects. Through this experience, we have developed a pragmatic process for setting an initial testing strategy that is as simple as possible and iterating on that strategy over time to evolve it based on how it performs. We have also settled on a style of testing that has proved to be very effective at reducing testing effort while maintaining (or even improving) confidence from our tests.
This talk will focus on some of our learnings and we will cover the different types of testing and how they interact, breaking apart the usual practice of testing all applications in the same way, the mysterious relationship between speed and confidence, how we were able to throw away the testing pyramid and a number of techniques that have worked well for us when testing our applications.
- Slides published to GitHub
- There will be a video, I’ll link to it from the GitHub when it’s published
The Object Mother, Test Data Builder, Anonymous Variable/Value, equivalence class and constrained non-determinism patterns/concepts can help you make your tests more readable/meaningful, more terse and more maintainable when used in the right way.
This talk will explain why and where the aforementioned patterns are useful and the advantages they can bring and show examples in code using a library I recently released called TestStack.Dossier.
- Slides published to GitHub