Test engineer


Usually has a high confidence level of his knowledge

In many occasions the app is something used rarely and not all is clear.

Target - find bugs.

Target - do some functionality or enjoyment.

Tries to figure how users will use this app.

Uses the app as a user.

Works in a methodological way, for example, tests feature rarely used by the clients.

Uses a small part of the app.

The tester has, in many cases, much more “app use time” than the client.

Uses when it needs it.

The testers know so much more about the app (from peers, training, papers) than the client.
Not only the functionality but also technical aspects.

The user knows only what he needs, and sometimes he will miss relevant functionality.

The testers probably are emotionally involved in the software more than the client. The tester wants the app to be a success.

The user just wants to finish a process.

Both testers and client has cognitive biases.
The tester, on the one hand, should be conscious enough to overcome some of the biases, but some should remain because, well, the clients have them.

The clients mostly are just being themselves.

A tester will debug the problem. Only the fact that the tester knows how is changing his or her POV.

A client comes over a bug and then… well, usually that’s it. At most try to find a workaround or call support.

Testers know about field conventions (like how a link is supposed to look like in the UI).


Testers might have relevant special knowledge like in UX, social behavior, university degrees.

Not mostly.

Tester use tools like sniffers.

The user will never know about that.

Tester gets paid for using the app

They do it for pleasure, for certain functionality. If it is for work, they are paid for a purpose that using the app is a tool for the purpose.

A tester gets over time a “feel” about the app. This might help him or her, but also make him blind for things a user will see at first glance.

For a user some aspects are seen at first glance.