On the subject of testing, the variety of definitions you hear in the industry is as diverse as the blind men’s descriptions of an elephant.
But in his important and thorough treatise “Integration Testing from the Trenches” Nicolas Frankel starts from basic definitions and develops the concepts of integration testing with a casual formalism that’s intuitive and fun.
The fundamental premise is that Unit Testing is the testing of one thing, usually a method, in contrast to Integration Testing, which is the testing of two or more things. Therefore in unit testing, the method under testing is preferably stubbed-in or mocked so the method’s algorithm is tested in isolation.
For more of the book review, click here.
The IT industry emerged as a popular and glamorous career choice in recent times. More and more individuals who have not been in the field want to try their hands at it. This is great, because technological inclination, fairly good pay, global outreach, challenging positions and scope for innovation are a few plus-s of an IT career.
In this context, the go-to branch of IT that attracts everyone is QA or of the software testing stream. This is perfect too, because QA is a great career choice in itself with lots of advancement opportunities. Or QA can be your introduction into IT that helps get firsthand knowledge of other areas, to determine your true calling in IT.
All good so far, but the question is “HOW” to start and emerge successful? This is the very question we will address in today’s article. To read more click here.
Configuration management is the foundation that makes modern infrastructure possible. Tools that enable configuration management are required in the toolbox of any operations team, and many development teams as well. Although all the tools aim to solve the same basic set of problems, they adhere to different visions and exhibit different characteristics. The issue is how to choose the tool that best fits each organization’s scenarios.
Taste Test, by Matt Jaynes, is a short, but instructive book that uses a simple scenario to compare Ansible, SaltStack, Chef and Puppet. On the recently released 2nd edition it adds new chapters on Docker, the communities around the tools, and how they fare on security. InfoQ took this opportunity to talk with Matt to know more about his thoughts on the tools and his approach to configuration management when consulting.
To read what Matt has to say click here.
In this TechWell interview, Michael Sowers digs into his rich experience in the industry, giving people tips for how to effectively communicate with higher-ups and how to make an impact in the testing process. He also discusses how best to become a trusted member of a team.
InfoQ: A lot of your talk that will be at the upcoming STARWEST presentation is about speaking like a test manager. What do you see as the first and the often most common mistakes someone makes when trying to communicate with a higher-up in a business?
Michael: Probably for more years than I care to admit, Josiah, I actually thought that those above me were interested in the details of my job and actually what my team did. I don’t mean that negatively, but it did take me awhile to understand that senior execs held different perspectives and were accountable for many different goals, of course, than what I was. Looking back now, that seems obvious, but certainly it didn’t seem so obvious. I guess I was just a slow learner.
Back to your question, what’s that first and most common mistake. I think it’s not framing your message from the receiver’s point of view. I wanted to tell my management all about those bugs that we had found, all about the test that we had automated, all the tools that we had purchased and installed, all the code we had cleansed or migrated, those types of things. But senior managers weren’t interested in that. They were interested in contributions to the business, which normally translate to how are you making things faster, better, and cheaper for me or for the customer.
To read the rest of the interview click here.