More and more, testers are being added to programming teams. We testers think that's great, and we're happy to be here. But we also have some concerns based on our interactions with development teams in the past. To make the transition easier, here's a letter pointing out some things you should know when managing testers on your development team.
Decades before web apps or smartphones existed, the concept of the separation of logic, presentation, and data layers in software made a lot of sense. That vision evolved into what we now call model-driven development, where rules, workflows, and dependencies are built once, as models in a centralized repository. It's the same basic idea, and it's just as useful, if not more so.
Though automation is often mentioned in the same breath as behavior-driven development, they are not equally important. If you want to use behavior-driven development, do just that: Work on getting the approach right, and forget about the automation at first. Here's why you should think of automation as more of a bonus to the BDD process.
Building innovative software faster and better is imperative to an organization’s success, so it makes sense to take advantage of DevOps. But what some teams fail to consider is that testing is a crucial part of the process. Without a “test early and often” mentality, DevOps would only be able to release software faster—not better.
The hype around the Internet of Things is at its peak. Should you bother learning the skills developers and testers require in this new field, or will it soon become just another trend that's fallen out of favor? Jon Hagar makes a strong case for why the IoT will be relevant even after the clamor dies down, and why its associated skills will serve you well no matter what.
As more businesses are adopting DevOps and demanding continuous delivery, it's important for testers to constantly upgrade their skills. By leveraging the right resources, including developer and application performance management tools, you can play a bigger and more collaborative role in producing higher-quality output.
Receiving feedback on your testing results should yield dividends in quality. And the sooner you get that feedback, the quicker you can start seeing improved and consistent quality and faster time to market. So the question becomes, why wait to jump on the automated testing bandwagon?
Testers who analyze quality in every aspect of the team’s deliverables also have a responsibility to mitigate risks and practical issues that are bound to come up, and help the team succeed in their product as well as at being agile. Here are five such issues that testers can help the team alleviate or avoid.
One of the major challenges in software development is ensuring that all the software components needed to do integration and end-to-end testing are available in the test environment. Implementing service virtualization can remove environment setup as a blocking condition—and enable project teams to release better software, faster.
Many companies creating mobile apps struggle to find the time to test on a variety of devices, organize bug reports, and resolve issues efficiently. Andrew White’s organization tried Ubertesters, a platform that provides a team of mobile testers and a set of features for feedback. This is his account of how it affected their test process.