Share three testing ideas for an ecommerce website.
I’ll share three things I might want to test for one of my favourite online stores, mightyape.co.nz
Same day shipping
If you’re in Auckland and order before 2:15pm, MightyApe offer same day shipping, for a fee. (They also offer for Wellington and Christchurch with different cutoff times).
I’m really curious about testing this feature.
Auckland is a big place. There must some address validation that takes place to see if same day shipping can be offered.
- If I put in a rural delivery address, can I still purchase same day shipping?
- I have a friend whose property lies half in Auckland, half in Waikato - what will their address do?
- What about a Waiheke Island address? It’s in Auckland - but it’s an island. It takes a boat to get there. Same day shipping still apply?
Another interesting thing to test would be the time cutoff.
I add the items to my cart, and apply same day shipping before 2:15pm - but I don’t complete the purchase straight away.
If I then complete the purchase well after the cutoff time, do we have any validation? Could I pay for same day shipping but not be able to receive it?
Another feature MightyApe offer is a wish list.
I think there’s some interesting stuff to test around here.
Firstly, is it easy to add stuff to my wish list, and to see if I’ve already added something?
What happens if I want multiples of the same item?
If I buy something from my wish list, does it disappear from the list - and should it? I think I’d expect it to.
What happens if something is on my wish list for a long time - so long that the item goes out of stock. Will it stay on my wish list? Maybe MightyApe could offer alternatives in this case?
You can also share your wish list - I’d want to test what the email looks like, and preview links in social media.
Your wish list can also be private - I’d want to do some security testing around this to make sure there’s no way to view it when not logged in.
They also offer alerts when items in your wish list go on sale - which I think is neat. I want to test this function, but more importantly I want to use it!
Wrongly priced items
Many years ago, I worked for a department store.
A set of cutlery was incorrectly priced at $3.29 instead of the correct $329 - and so our manager at the time was obliged to honour that price. Someone got in trouble for that one.
I’ve seen similar things happen on online stores too, where an item is incorrectly priced, the word gets out on Twitter, and then people rush to buy a widget at an absurdly low price.
If I was a tester at MightyApe, I’d like to test scenarios around “what if this happened”.
The first thing I’d think of is alerting.
We could look at raising an alert if an item sells below cost price for example (if we have that information in our system).
Or, if an item has a sudden spike in traffic, raise an alert for that.
Secondly, will our site handle the sudden increase in traffic?
We should performance test for this scenario - we don’t want regular buyers affected by an event like this.
Thirdly, how do we handle this event once we become aware of it.
What tooling do we have in place to remove or update the offending item really quickly.
Can we bulk refund / cancel the offending sales (and is this legal?), and can we communicate this en masse effectively?
I think this would be a fun incident response / game day type exercise.