By attending a workshop on the topic by Alex Schladebeck
Switching roles with peers. Research about domain and discussion about usability for user with team.
By thinking like a newbie to the application every day with curiosity before starting!!!
Don’t let too much time pass between the times I set aside to do some!
Getting fresh eyes and perspectives from those not working directly with the project.
Environment, data, user, role, volume , basic workflow… permutations of all these
To keep exploratory testing fresh, one has to understand the domain and the main functionality of the application wrt domain & business requirements. And need to find out specific areas where we can contribute as a tester, which can be anything starting from concept, ideas, ways to implement new features, etc…
Small exercises scoped by component/features and a time box. This allows a high degree of rotation in people conducting the tests, more viewpoints in a shorter span. For extra fun give the tester a “role”. Test it as an engineer, operations analyst, support engineer or customer. This also allows customer support backlogs to be used as a source of real usage scenarios.
Have fun when doing it! It really accelerates creativity and imagination which,for me at least, are key when exploring🤓
Understanding the functionality and workflow of the application and exploring the application. Do testing with both positive and negative mind. Notably, we need to forget about requirements and conditions.
Maybe there are some ideas you can use - or maybe you’ve some to share?