Related Content
Making Testing Visible Most testing work is invisible—something that happens inside your head and leaves no artifacts behind. This generally leaves testers feeling like no one understands what they do all day. Here are some ideas for collaborating with your coworkers so they can see—and start to understand—your testing work. |
||
4 Takeaways from Agile + DevOps East 2018 With a week full of sessions, tutorials, training classes, and events, the Agile + DevOps East software conference had plenty of takeaways. Here are four highlights, including discussions about agile estimation, finding your ideal job, some challenges to advancing test automation, and leading self-organizing teams. |
||
Agile and DevOps Bring the Focus Back on Quality As companies move to agile and DevOps, silos are coming down and there is more interaction and collaboration among teams. Quality is also becoming everyone's responsibility for the entire software development lifecycle. Quality is more than just testing: Consider a quality value stream along the overall value chain. |
||
The Cost of Software Testing Testing is regarded as the number one bottleneck in the software delivery process. Most people simply conclude that developers are value centers, and testers are cost centers. But developers' work also brings cost, and—more importantly—testers' work also brings value. It's time to reframe our thinking about testing. |
||
A New Approach to Load Testing with Browser-Level Users Since the inception of load testing, the approach has been mostly the same: simulate the traffic of an application by creating load at the API level. But there have been market shifts that make load testing with browser-level users more feasible—allowing us to test with real load and measure true user performance. |
||
Frameworks Are an Agile Leader's Best Friend With a framework in place, engineers can stop worrying about everything that framework does for them. Your team can focus on solving your business problems instead of building yet another solution to an old problem that's been solved before. Look around and identify the mistakes your team is making over and over. |
||
Continuous Testing Is Not Automation Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production. |
||
Lessons Learned (and Unlearned) at STARCANADA 2018 With a week full of sessions, tutorials, training classes, and events, the STARCANADA software testing conference had plenty of takeaways. Some highlights: what jobs will look like in the future with AI, why testers should lead efforts to make quality everyone's responsibility, and the importance of unlearning. |