The sentiment of an app test

The project manager is responsible. Product responsibility. Testing only needs to show the problems found in the test. Truthfully reacting to the problem. Who is responsible for who has the right to decide not to go online. So they bypassed the test directly.
App on-line let me learn a lot of things, see a lot of things, but also a lot of sentiment. This is what I have never experienced in my previous Test career. I have seen my shortcomings and need to correct them. People who have come into contact with a variety of personalities. Anyway, I've seen it.
My sentiment:
1. Testing is not about doing your job, it's about dealing with people of all kinds of character.
2. I have done a very bad job in this test. I'm not happy myself. and product quarrel, in the work to set up the enemy.
2. Test the degree of work.
3.bug of Quality
4. Test pass the standard.
That's the way things are.
This test is an app project. Time is tight. Wednesday received a list of tests. Friday was a knot in the evening. Only 3 days of testing time.
Encountering an aggressive product is an experience of what.
My interpersonal communication issues are highlighted. I will not communicate with the product. will not communicate with development. I am a very gentle person, met an aggressive person, my first reaction is to oppose her. This makes the subsequent exchange of 2 people very unpleasant. Formed an enemy in the company's colleagues. That's not good.
I envy other testers who talk to other people when they need to talk. You should lose your temper when you lose your temper. I'm not sure I'm doing this. Too blunt to communicate well with developers. Too soft to lose your own test principle.
The story took place in the evening of Friday. They're going online. I can't get out of this one. The results of the test pass. First, because there are currently recommended contacts and can not modify the picture of the problem is not resolved. Two is. My heart is really flaky.
Thursday test found the problem. Friday is gone again. Many bugs are not reproducible or external due to their closed state. And some are designed so.
The problem that cannot be reproduced is that the problem was discovered when the test was made and the problem was not reported until the development was resolved.
The problem with external causes is that the app relies on other interfaces. Problems with the network.
Other words. The Thursday test problem, Friday no longer appears. The intuition tells me that such a system is very unstable. New problems may arise after the launch. Not stable. But for the time being, the problem does not arise. I can't say anything. It is a state of feeling that there is a problem but that it does not matter. I dragged the report out of the test. The product is aggressive, let me write the report of the test pass. I refuse, procrastinate, and there are all sorts of unpleasant things. So unstable and so slow system, they dare to take out on-line, which I have never seen.
At the same time review their own testing work, in addition to development and product communication. The problem with my test work is:
1. My test thinking is unclear
2. My test summary is not good
I was testing cross-border payments in the morning of Wednesday. I started testing the app in the afternoon of Wednesday. Submit bugs found in the test environment to the defect management system.
Wednesday night production, but not externally developed.
I started testing in the production environment in Thursday, and I tested it all day and found 25 bugs. Go to class in the evening of Thursday.
Wednesday night overtime, Thursday back home very late. My work efficiency has been very low in Friday.
Friday development changed something. Give me a new version and I'll verify the bug. A small number of test bugs were submitted.

The sentiment of an app test