concept behavior in category software development

This is an excerpt from Manning's book Writing Great Specifications: Using Specification by Example and Gherkin.
Many delivery teams burnt by over-specification discard it in favor of an implementation-first approach, eradicating any up-front practices. An implementation-first approach optimizes for writing software without dealing with wasteful documentation and specifications. It rejects huge design commitments before customers prove they want the solution—and the only way to prove it is to hack some code together and release it as soon as possible, rejecting any process that doesn’t help write production code. For example, Extreme Programming advocates use no extra design documents and let the code speak for itself. Running code doesn’t lie, as a document might. The behavior of running code is unambiguous.
The ubiquitous language fuels the domain model. Having a shared dictionary of important business concepts creates a platform for discussing data, behaviors, and relationships within the model in a meaningful way, with a certainty that everybody is on the same page. In the journey-planning example, the team thought that a destination was the same as a street; but it turned out that users assumed there are other kinds of destinations, such as buildings and points of interest. Having established a baseline, the team can use the common language to establish clear relationships between the concepts of destinations, streets, buildings, and points of interests.

This is an excerpt from Manning's book Test Driven: Practical TDD and Acceptance TDD for Java Developers.
In addition to not introducing defects with our changes to the code’s internal structure, we also don’t want our refactorings to add functionality. That is, refactorings should preserve behavior.
It’s trivial to verify the presence of components on a page with the WicketTester. How about testing for the behavior of those components when we try to interact with them? We’ll do one better than just answering that question—let’s see some concrete tests that demonstrate the answer in action.