There are some rules about WHAT we are going to test on every project, no matter the type of project. So, the essential things we will test, and test against, are usually assumed. For example, requirements.

Beyond those givens, the right things to test depend on project constraints, and what the stakeholders expect. These fall into two categories: constraints and expectations.

In situations where stakeholder expectations are the key proof, testing against what the system does, without being concerned how the system does it, is sufficient. But, think like a tester! Just because the stakeholder is happy to see the functionality described in the requirements work as expected doesnt mean that testing is successful, or that youve been a success as a tester!!

What else should we test in this situation?

Provide examples where functional testing will be not enough. Explain your answer.