Hello sir, you showed only one module like registration here..do we explore each and every module in this testing? Also who performs this testing -team lead or other tester..? Is it mandatory to use tools like u have shown or we can use only Excel also..
You can perfectly use Excel for ET. There are a few things that are important. First answer what you are focusing on so your testing sessions have a bit of structure and limitations. Your focus should make it possible to determine when you are finshed testing. Second while exploring the application you need to take notes about the stuff you see (bug, insight, problem, suggestion, test idea and so on). You can describe your goal (test charter) and your notes in excel. Last but not least you have to summarize your session and write down key findings (again you can do that in excel if you want). Anyone on the team can do exploratory testing, even someone with zero testing experience. The essence is learning about the application, designing and executing tests at the same time. It's actually easier than creating scripted testcases. A testmanager might be needed to make newbies more effective in ET. Which modules to test? Good question! Testing is all about risk detection. ET can help in determining which modules have more risk of creating problems. ET should therefore focus on these areas. It might be benefical though to go through each feature/module at least once, to have at least some idea whether that feature/module has severe risks or not. But it is not an obligation at all. The team might decide that it's not a risk that needs to be investigated.
No. Because an automated script doesn't test anything. It just verifies something. But automation is a execution method that can help with ET. It's part of ET, not equal to ET.
Even I m confused.. he said explore means we learn the software..and then he is adding 40 characters into the textbox, but only valid credintials supposed to be added..
We explore the application by interacting with it. And whenever we find something interesting you have to ask yourself: is this a bug or desired behaviour? There are artifacts that can answer our questions like a document with the requirements or acceptance criteria or people like a business manager.
Great informative video, excellently explained!
Thanks
Need to write or record test cases for exploratory testing?
Thank you very much for video and the drive link which contains awesome resources.👌
Thanks
Excellent teaching
Informative video. Got to know good tools to use for exploratory testing.
Thanks for the feedback, consider sharing
Thank you so much for the video!
Thanks for the awesome feedback
Explained very well.
Thank you brother,you are doing great job
Thanks for the awesome feedback
Sir you are really a great.
Thanks very helpful information and notes you provided
Thanks for the awesome feedback
Hii this is nice session
WHAT IS MASKING DEFECT AND LATENT DEFECT
thanks, very well explained
Thanks for the video and the documents
Glad you like them!
Hello sir, you showed only one module like registration here..do we explore each and every module in this testing? Also who performs this testing -team lead or other tester..? Is it mandatory to use tools like u have shown or we can use only Excel also..
You can perfectly use Excel for ET. There are a few things that are important. First answer what you are focusing on so your testing sessions have a bit of structure and limitations. Your focus should make it possible to determine when you are finshed testing. Second while exploring the application you need to take notes about the stuff you see (bug, insight, problem, suggestion, test idea and so on). You can describe your goal (test charter) and your notes in excel. Last but not least you have to summarize your session and write down key findings (again you can do that in excel if you want). Anyone on the team can do exploratory testing, even someone with zero testing experience. The essence is learning about the application, designing and executing tests at the same time. It's actually easier than creating scripted testcases. A testmanager might be needed to make newbies more effective in ET. Which modules to test? Good question! Testing is all about risk detection. ET can help in determining which modules have more risk of creating problems. ET should therefore focus on these areas. It might be benefical though to go through each feature/module at least once, to have at least some idea whether that feature/module has severe risks or not. But it is not an obligation at all. The team might decide that it's not a risk that needs to be investigated.
is it possible to automate exploratory? if yes can you explain
No. Because an automated script doesn't test anything. It just verifies something. But automation is a execution method that can help with ET. It's part of ET, not equal to ET.
Thank you for the video, you have covered lot of information. Would you don't mind can you share mind map .?
My bad, i see you already added.please ignore my request
I think mind map for exploratory testing is missing, it would be helpful if you could share.?
What software are you using for the expand/contract tree view? 🤔 Thank you!
Mindnode
In this testing we are knowing about an application, then how we can find the bug??
We explore it
Even I m confused.. he said explore means we learn the software..and then he is adding 40 characters into the textbox, but only valid credintials supposed to be added..
We explore the application by interacting with it. And whenever we find something interesting you have to ask yourself: is this a bug or desired behaviour? There are artifacts that can answer our questions like a document with the requirements or acceptance criteria or people like a business manager.
thank you