Do you check the code on an intuitive level or do you describe cases? Are acceptance tests and functionality demonstrations conducted?

When verifying requirements and functionality, I use both approaches: intuitive and case-based. The intuitive level helps quickly identify obvious discrepancies and errors, while describing specific cases is a more formal and systematic method that allows testing the system's operation in various scenarios.

Acceptance testing (AT) is always conducted to confirm that the system meets the customer's requirements. This usually includes demonstrating key functionality, verifying business logic, and user interaction. The demonstration helps stakeholders see the actual operation of the product and provide feedback before launch.