Tester vs Acceptance Criteria Checker

Tester	Acceptance Criteria Checker
Requirements
A tester knows that even if the product meets the requirement to the T, the product could totally suck. So, they do not rely too much on the requirement to measure product quality.	A checker is heavily reliant on showing the acceptance criteria is met. They won’t go into testing without a document.
Test Cases
A tester writes product based test cases. They ensure test case longevity with data set up and tear down info for fast execution	A checker checks the acceptance criteria. They do not know they need to plan for the future, they focus on the bare minimum.
BUGS
A tester works to find issues that wont show on the surface	A checker works to find issues inside and within the acceptance criteria.
Purpose
A tester explores the product and understands what it does and how is does it.	A checker checks the surface and within the boundaries of the requirements.
Focus
A tester contributes to making a product better	A checker tries to find where the product is broken
Product vs Project
A testers job never ends. A tester feels responsible to support the product through its life	A checkers job ends with the project
Test Data
A tester works to create, edit and maintain the data required for testing	A checker is dependent on the developer or the business to provide the data
Ex – Sign Off
A tester relies on product and architecture knowledge to understand the state and stability of the product and little on the regression tests	A checker relied on the PASS and FAIL test results.
Ex – Superman vs Clark Kent
A tester will go deep into what superman is all about, who are his parents, what is his real identify and all that jazz. They understand that Clark Kent and superman are the same person so focusing on clothes is literally scratching the surface.	A checker will only observe that obvious differences of the superman costume. Clark Kent – wears his underwear inside Super man – wears his underwear outside
Ex – Menus or drop-down lists options
A Tester will explore where this data is stored (in the database or hard coded into UI)	A checker will make sure the list of items shows up as listed in the requirements.
Ex - Authentication of the user
A Tester will find out where the registered user information is saved and make sure the passwords are salted too. A tester will also find out how the user session is authenticated and terminated in the browser	A checker will make sure the registered user is authenticated with valid credentials.