Hello Readers, thank you all for your emails / comments / thanks, and also encourage them and learn that they are taking a shower. While this is going on, I am more responsible for posting some good stuff. I always try and hope I can spend this time too. “Monkey test” is a phrase that every evaluator should find and, thank God, I also found it in the first week of my career. “Sarah will do monkey tests for a while …” announced the manager at the meeting, a bit embarrassed, because he didn’t know what it was about. Once the word monkey came up, I felt like the company hired me for that. . However, I made the peanuts that I should get according to the admission letter. I recently came across this great link http://www.softtest.org/sigs/material/nnyman2.htm, it says great about monkey testing. Just through this link I understand the concept of an automated monkey tester — I am sharing experience like this, such as Monkey Tester __ Monkey Tester and Peanuts ____ after testing built-in products for various versions and fixes, I have formed a situation in which my opinion of the main place is wrong, and once it shows up in the whole regression cycle, it takes less time to test (compared to the week my manager usually gives). I know sitting for a long time and continuing to run the case is painful, because even after doing this my peanuts never went up. 1) I developed a strategy to look first at the areas that are most important to the case. And coexisting bugs (coexisting bugs, isn’t that fun?). 2) I tested these areas and was lucky enough to find important crash / crash / error conditions and blocked the relevant cases and was able to provide the expected results in the expected time. (I still have to work on the weekends) 3) My peanut count is still the same! Over time, experience, learning and mistakes continue … I learned a lot and they called me a “good evaluator” [good evaluator is a relative term, my predecessors and peers I think yes, it is not my own assumption that I am good] __ (like) Monkey Tester and the end of Peanuts! (I quit that job) ___ Now, how will I test when the product is delivered and the time is less than the actual planned or suggested time? 1) Ask developer / leader / manager / release notes or all of them a) Yes Bug fix version? b) Is it a feature update or a new feature addition version? c) What modules / features / functions the encoders have been exposed to. d) What are your views on existing robust and non-robust areas? product. e) Will it be injected into the market and what are the common characteristics that will be widely used by end users? f) You can make your own list, but make sure you don’t waste time collecting junk information. 2) In turn, I will tell them a) What is my understanding of the information I received from them? b) What is the scope of my test? c) What are my testing limits. d) Since there is less testing, which can affect customer time more than planned. e) If more time / planned is given, what is the change in vector on the graph? (For those managers who are satisfied with the graphical data instead of the numbers in the Excel table) f) What or how much can they expect at any given moment, nothing more. 3) Do not interrupt your relationship with developers / managers / leads / anyone else at such a critical stage, understand that some people are sick and you have to pass them. b) Tell yourself that you must do your best to achieve the success of the product. c) Don’t think monkey test is enough, even if you encounter errors instead of running your test case, it may be because your test case is not well built or something important is missing. d) Please pay attention to your health, peanuts will rise late at work, either for you or your GP. e) Feel free to report that you didn’t get it right, if you did, this will put you in a safer mode, in anticipation of some negative customer feedback (as usual: D). f) If you can plan something similar, please ask for a higher salary or a higher or better interest rate than this. g) If you are not recognized despite your smart work, do not leave the company. I can quit smoking! “When you learn more and more and get out of the’monkey trial’ period, you will still be called an adult monkey” Thank you for joining as a tester, but let them know that all testers, whether lucky or unlucky , Both have become/do the monkey test, and they must also learn from it. What to do and not to do and all the other points mentioned here are my opinions based on my own experience, learning/mistakes may vary from person to person. I have more perspectives and learning, but I want to keep it short. Constructive comments are largely welcomed, but don’t irritate (me) the monkey with destructive comments: D.Btw, I wanted to talk to you about https://bugasura.io . Its a tool that modern teams use to track bugs. I recommend you take a look at it and see if its suitable for your needs*