Related Content
The Test Automation Design Paradox Testing and automation have various paradoxes that are interesting to look at for insight into the challenges and limitations of our profession. Hans Buwalda describes these paradoxes and offers methods to bring about cooperation in teams, helping them achieve great automation results together. |
||
The Basis of Test-Driven Development: Writing Effective Test Cases Too often, test-driven development still initially focuses on coding aspects, not testing. The first step in a test-driven approach has to be writing effective tests. It's not enough to simply ensure good coverage; effective tests should also confirm that decisions made in the code work correctly. |
||
STAREAST Receives Glowing Reviews from This Year’s Attendees TechWell pours hundreds of hours into STAREAST each year, and for the most recent conference, we saw a medley of interesting articles appear afterward written by happy attendees and vendors who represented their companies at the Orlando-based event. |
||
How Continuous Integration Can Save Your Team Substantial Time and Effort Continuous integration is all about the feedback loops between your developers, testers, product owners, customers, and everyone involved in your organization. That’s great to write as if it’s gospel, but what can continuous integration and continuous testing do for you right now to improve efficiency? |
||
Why You Should View Every New Workplace Challenge as a Confidence Booster New challenges can certainly be rich learning opportunities, whether or not the effort is a success as anticipated. It's time to view every new challenge as an opportunity to boost confidence. You certainly won't lose—you only stand to gain with this approach. |
||
3 Steps to Nurture IoT Development and Testing As more devices connect to the Internet and engage in machine-to-machine communication, QA management must cultivate an understanding of the IoT and how to create software for these connected items. Sanjay Zalavadia describes three steps to nurture IoT development and testing. |
||
The Art of Giving Feedback Your Team Will Act On Giving good feedback is hard. A common pattern we follow—especially when we have to give negative feedback—is starting with something positive, addressing the problem, and ending with something else positive. But it turns out this "feedback sandwich" method isn't the most effective. Here are some better ways. |
||
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas. |