QA tester COOP

Getting experience is all we do everyday, nothing else. Life is to experience.
` P2s8e'Q$t^;a f0
n$f gJ@&Y+@N]'}0One month experience of working as a software tester seems not bad, even though the job is just like an entry level position, running test scrīpts created by others. The challenge is that when an issue occurs, you have to analyze what kind of issue it is. Is it an application issue, a scrīpt issue, or configuration problem of your tools.51Testing软件测试网v*AgDghB
51Testing软件测试网S zB{"hDH
Application issue leads to bug report to developers. scrīpt issue throws over to the scrīpt creater even if you already debugged it and probably it is just a misspelling. Other than those, you have to figure it out and make some adjustment yourself. Anything you do needs careful detailed documentation if you want to be efficient.
i3rtbjq8g0
@ cu `t,@)L.aV0scrīpts can be running for hours and hours. Issues just come out during the running. When do you need to stop the scrīpt and do your documentation? Too soon it will be less productive and boring. Too long you will possibly forget something. Even worse if you can not finish all the issues before the end of the day. You will have to start it over the next day in this case.
E4@.gYV`&z:q0
;R$s H$l7J0Well, I think it is just enough for me to start making documentation. 3:30pm already. Team lead came to ask me my progress. I have not finished one scrīpt today. But two long lists of both kind of issue are at hand now. Let me generate them and show some achievement for today.
| eucc[0