Here I have created a basic web application that is, let's be honest, a bit rubbish.
In this activity the client has a website that was being developed by a third party who have recently had to cancel the contract. The client has been given the code and a test instance but unfortunately not a lot of documentation. They needs to know about the state of the website and you have been brought on board to help explore and test the site.
The client has made the limited documentation available to you in this requirements page.
Review sites may be a dime a dozen out there but this website encourages you to be harsh and scathing then see other people's bitter and angry reviews.
Look at the user flow to log in, post a review and then view it
to test for any blockers.
Explore the Admin page with a mix of different types of characters
to discover whether the site title can be correctly saved.
Explore Products page with products that have multiple reviews
to discover whether they are correctly listed.
Look at resizing the pages to test the site's responsive design.
Explore the website with text-to-speech accessibility controls
to discover whether the website has been designed suitably for
someone with visual issues.
A key output of exploratory testing is your report.
This could be in the form of a document created by a tool such as Xray Exploratory App, a Google Document or even just a few notes jotted down along the way.
I have provided a page where you can share your reports and also view other people's exploratory testing reports. If you are new to exploratory testing, it might be handy to read what other people have put together.
Please be aware that I've not implemented any sort of moderating tools.