Testers regularly look at the requirements to find out how the product be supposed to behave. Often these requirements are related to the functional & some non-functional attributes including performance, safety, some elements of usability tests, etc are developed with the expected results that bring into line with the requirements of the product. There is a clear line of writing requirements for testing. As testers, as you proceed with the execution of the tests, there may be cases where you feel distress or frustrated with aspects of the application under test. You may feel a range of emotions as they test the application. At that time, what are you doing? Do you listen to your feelings or go with the script, looking for expected behavior as described in the test cases that is walking. If the test produces the expected behavior, while mixed feelings you have experienced in the coursework of testing, what would you do?As a application tester, is it necessary to give importance to their emotions & feelings that you find in the coursework of the test or is that these "softer" aspects of your automobile in front of the door before beginning a test campaign? Do the tests purely based on logic & writing requirements in peace? Is there any value to listen to what your inner "voice" & the feelings are trying to say what test the application?In my view, the testers need to listen to their feelings in the coursework of the tests. That said, some tests may need you to basically follow the script & cease at the control of what is said as expected behavior. However, the lovely news is that most tests are the feelings & emotions to be a useful aid added to the testing efforts.