4) Test your questions
once you have finished writing your questions, ask them to yourself, to your colleagues or friends. Take notes about the type of answers you're getting.
remember, your job during the interview is to look for EVIDENCES, so if the answers you are getting are not providing you any evidences, then you need to refactor your questions.
Part Three - the interview
All right, you are about to finally meet with the candidate face to face. And if you're using Skype…
…dinner, drinks, or just in the hallway. A special highlight was whengave a Test Driven "training" in the Community Room. The crowd loved it.
Following CfgMgmt Camp # training and the Infracoders London Meetup, where he presented "TDD with Chef". Between the beers and wide-ranging conversation, the meetup was a splendid cap to some seriously productive training …headed to for
…to help alleviate this problem. Wrapping things like Source Control Management, and Test Driven Development around your automation allows you to 1) have tested infrastructure code, 2) audit what is changing in your environment , 3) have an audit trail of who changed things, and 4) know exactly when it changed. Compare that to legacy change control processes if you will.
If you want to be successful with any large scale organizational change, you need to assume that everything you are currently …
Support for Test Driven Devops - Using custom matchers to make sure you don't break configurations.
List of - There are too many of them. that to JS
Never Write a Web Scraper Again - A visual approach to scraping.
We use RSpec over Test::Unit because the syntax encourages human readable tests. While you could spend days arguing over what testing framework to use, and they all have their merits, the most important thing is that you are testing.
Feature specs, a kind of acceptance test, are high-level tests that walk through your entire application ensuring that each of the components work together. They're written from the perspective of a user clicking around the application and …
4. Test, Test and Test Some More
Litmus to test all our emails before they go out. But you can't just rely on a service. You have to pick up a device. Around the office each of us has an iPhone and iPad at our desk. We have several and devices lying around. While relying solely on an email testing service is easy, it's amazing how much just looking at an email on a device can …is crucial ''as we showed in our little parable. We use
However, it can be tempting to also stub parts of the System Under Test. This should be avoided.
Why not stub the System Under Test?
The goal of the guideline " Don't Stub the System Under Test" is to help us use tests as a …
1. Test, Test, Test ... and Test Again
We learned a rough lesson just days after releasing Ink. We sent out this month's Notable newsletter. Looked great on desktop email clients, but not so hot in mobile, especially iOS. And we rightly got called out on it. Check out how it looked on iPhones:
What happened? We tested using Litmus and all looked good. But we could've saved ourselves a bit of a headache if we just looked at an iPhone and not relied solely …
Continuous Delivery: Reliable Software through Build, Test, and Automation
byand David Farley
The of Full Engagement: , Not , is the to and Personal Renewal
by Jim Loehr and Tony Schwartz
Failure Is Not an Option: from to 13 and Beyond
by Gene Kranz
Team Geek: A's …
…to catch the users attention.
- Ensure it serves a purpose.
- Ideal placement of your code (on a motorway billboard is not very useful).
- Size for readability (typically 1inch or more).
- Tell the user what they stand to gain.
- Test it!
Note that some customisations such as embedded logo's may look cool but won't necessarily read as easily so it is always a good idea to test your QR code before the final release.