testing - What should a tester report? -


I have a web site that I'm making for a client now I have a tester on this project.

I think the testers really need to! I can not test my code. I also appreciate the value of a new set of eyes. But what is the desire to report?

It is easy to say that everything should be informed, but there is no need to filter any unimportant requests between me and the examiner, the tester does not know the system nor the targeted user is well . He is telling me the work, not the project manager. I think it will change soon, but until it does not happen, what do you recommend? It seems that our users have never used full before, and they are dumb in the form of rocks.

The problem I have is that the tester suggests that everyone is being accepted automatically and I have been handed over

I have many issues which I leave my jaw and say, "Are you serious? Should this be an issue?"

ex: Need to add text to the top page that says "* = Required" for the required fields.

Have you ever felt like this? How do you work with it?

For now, I am just saying, but I am making it clear I do not agree.

It seems to me that your testers are doing the right thing while testing an application Users of level can not even assume expertise. If a user can break something, they will.

You and your tester should work on a serious scale. Outlets (which works with any Internet experience / will never hit) will be considered less priority and sit on the back burner unless you take out the high priority items.

... Never less, those outlets still need to be logged because they can definitely come back to bite you in the ass.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -