1. Getting Mobile Testing Right
Comprehensive mobile application testing shouldn’t just be an afterthought in your software development lifecycle. It has become a necessity. If you have a public facing web application, you have mobile users—and you’ll need to address these users by conducting realistic mobile performance tests.
Accounting for the number of devices, browsers and operating systems in use, along with mobile constraints and usage habits, can seem incredibly overwhelming. In this article, author Sanjay Zalavadia explains how organizations can combat the complexities mobile users introduce to avoid damaging the company’s reputation, revenue and business continuity.
In the software testing industry, time is like Firefly episodes: there just isn’t enough. It might come as a surprise, then, that developers and testers in organizations without service virtualization waited an average of 32 days for everything needed to move forward with work (voke inc.’s 2015 Market Snapshot Report on Service Virtualization).
In the famous words of Kimbely “Sweet Brown” Wilkins, “Ain’t nobody got time for that!”
Ensuring that all the software components needed to do integration and end-to-end testing are available in the test environment is one of the major challenges for software development teams. In this post, author Bas Dijkstra discusses how teams can implement service virtualization to remove environment setup as a blocking condition and to release better software, faster. Take a look!
If you’re doing test automation today, chances are your tests are still dependent on some amount of working code in the testing environment. However, with the DevOps movement and push for continuous delivery, the way we have done automation in the past has to evolve. You must transition to continuous testing.
In this TechWell post from author Adam Auerbach, he explores the nature of continuous testing and explains its importance in software development lifecycles. Auerbach also provides some key tips for introducing continuous testing into your organization. Read the full write-up here.
Whenever you’re “benched” or kept from the action, whether you’re a part of a baseball team or even a software development team, it’s imperative to use this time wisely. To improve upon your skills as a software tester, you don’t necessarily have to be working on a project. In fact, the time between projects, or “bench time,” provides an excellent opportunity for reflection and growth.
This article from Software Testing Help (STH) outlines nine different ways testers can successfully utilize their bench time. From updating project wikis to learning automation tools, STH’s suggestions provide a solid outline for testers at any level looking to make the most out of their bench time. Check it out.