Along with the festivities of the holiday season is the joy of shopping. We have so many options today with online, mobile, and in-store shopping. Changing consumer behavior and demographics mandates that retail technology must continuously evolve at a very fast rate.
This blog post covers some of the key business and technology testing imperatives in the retail industry. Testing the right systems and integrated touch points, optimizing test coverage, using the right tools, benchmarking user performance, and ensuring multichannel scalability and security are core components of a holiday testing strategy.
Find out what testing strategies are naughty or nice here.
Around 5:00pm PST on November 23, the Domain Name Service records for at least some of the sites hosted by the online classified ad and discussion service Craigslist were hijacked. At least some Craigslist visitors found their Web requests redirected toward an underground Web forum previously associated with selling stolen celebrity photos and other malicious activities.
It’s a scary thing for a tester. After all, you can walk through the functional and performance capabilities of your site all you want, but how would you know if something like this had happened? Especially in a less-popular area of the site? That’s where a strong synthetic user monitoring solution like NeoSense can help – its ability to traverse complex, multi-URL transactions can provide an early warning system.
Check out more details of the Craigslist DNS hijacking.
As a tester, you want to get the full picture so you know exactly how your end users are thinking and feeling. The absence of customer complaints doesn’t necessarily mean customers are happy.
This blog post describes two cases where the lack of customer complaints was misinterpreted as customer satisfaction. Stephen, a VP monitoring customer complaints, noticed that his metrics were on the upswing. Meanwhile, Carla, a Director, assumed here valued customers would tell her if there were problems. Both learned the hard way that conclusions like these can lead to disastrous results.
Check out the details of their stories here.
Here’s a discussion that you may be able to contribute to about the purpose of test-driven development, or its intended usefulness.
“I know that test-driven development is a style of development where you write tests before you write code. I can see how this would help structure a person’s thoughts with regards to what they need to code. The question is this:
Is the purpose of test-driven development purely focused on improving the quality of code, or is it more about spending time up front with the intention of saving time in the long run?”
What do you think? Share your thoughts.