Some time ago I personally didn’t know what was exploratory testing or neither what it was useful for. But then I found a really good example that showed me in a very easy way how this technique can be described and change a bit my perspective about the concerns related to this technique.
Let’s imagine you want to visit a new city. If you use a planned approach ( which is still considered the “common” way the “most useful” way to do it), what you will do is the following:
How do scientists demonstrate that a drug or vaccine is effective? Putting it to the test. It's your only choice. And, if you're reasonable, you'd never use medications that haven't been thoroughly tested. So, why don't you test software as thoroughly as you should?
Are you looking for Exploratory Testing Tools to help you in documenting your testing session. Check these Automated Exploratory Testing Tools
We have all seen articles recommending explorative (exploratory) testing as a way to spot bugs faster and earlier in the development process. You may also have wondered if that is really the case. On the surface, ad-hoc testing offers many of the same benefits as exploratory testing. However, there is a small difference between exploratory and ad-hoc testing by definition. And knowing the difference would save you from potential miscommunication. Let’s compare
The shift towards microservices and modular applications makes testing more important and more challenging at the same time. Learn more here.
API endpoint when you send the get request to that URL it returns the JSON response. In this article, I am going to use postman assertions for all the examples since it is the most popular tool. But this article is not intended only for the postman tool.