In the past few weeks, I’ve been getting daily emails about early access to retailers’ Black Friday and Cyber Monday sales. Which got me thinking about two things: one, I hope retailers are prepared for the even earlier onslaught of online traffic, and two, the high stakes for site performance on the two busiest shopping days of the year.
The annual Gartner Symposium/ITxpo in Barcelona, Spain, is a great pulse check for what's on the minds of CIOs in large companies (like banks, utilities, telcos, governments). It's not necessarily the place to see the absolute latest technology, but it is the place to see what organizational problems CIOs are trying to solve with technology, and what companies are rolling out next year.
Consumerization, digital experience, DevOps, mobile, fragmentation, and microservices have changed how software products are architected, how they’re produced, what they do, who uses them, and those users’ expectations. As a result, there’s been a massive shift in testing requirements, both in terms of what we’re trying to achieve and what we need to do.
Note: Back by popular demand, this is a repost of a previous blog by Antony Edwards.
SciFi worlds from the 1980s always included super powerful, intelligent computers that you could talk to. By the late 90s, the vision had moved on to worlds where everything is a computer and connected; maybe even us. And it’s this ubiquitous computing that I think is the most exciting and interesting part of technology: new device categories.
In my last post, I described a test team structure that I've seen several companies (which I think are real thought leaders in testing) successfully implement over the last few months. Included in that structure is the sometimes controversial statement that scrum teams should have dedicated, professional testers; that is, we shouldn’t make developers responsible for all testing (though they should be responsible for white-box unit testing).
How should we structure our test team? This is probably the most common question I hear when talking to test leaders about what's on their minds.
A new study of 600 testers reports that 91 percent of test teams are struggling to meet increased user expectations compared to 12 months ago, and 66 percent said that test automation needs to expand beyond just test execution to keep up with business demands. The new study, conducted by Kickstand across the U.S. and U.K. on behalf of Testplant, generally identified that app dev teams are feeling the pressure to innovate and deliver high-quality user experiences quickly.
Back in May, British Airways suffered an outage that cost them £150 million and left 75,000 people stranded. After days of speculation, BA announced that the outage was due to an engineer causing a power cut. Surprisingly, BA suffered another outage in August 2017, with its spokespeople announcing that they experienced “temporary check-in problems” but the “earlier problem has been resolved”.
Over the past few weeks I've spent a lot of time playing with the various "deep learning" libraries that are available as we prototype the best ways to use this exciting new technology to testing.
Gartner Symposium. I always enjoy it. Of course it's a deluge of buzzwords and bombast, but there is substance beneath, and I enjoy thinking about the implications for teams creating software in the future.
This morning I was listening to a talk from someone in the Oil and Gas industry who has actually deployed machine-to-machine, i.e. what everyone talks about as the future of Internet-of-Things but very few have any practical experience of. It was an interesting talk.