# On behavior verifications

DevFeed: [On behavior verifications](<https://devfeed.tech/articles/on-behavior-verifications-27280.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201709/behavior-verifications/>)

Published: 2017-09-06T00:00:00Z

Content type: article

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Refactoring](<https://devfeed.tech/topics/refactoring.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>), [Smoke Tests](<https://devfeed.tech/topics/smoke-tests.md>)

Tags: [integration-test](<https://devfeed.tech/tags/integration-test.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [test](<https://devfeed.tech/tags/test.md>), [tests](<https://devfeed.tech/tags/tests.md>)

## AI overview

A developer recounts refactoring springmock after its double-definition parsing class accumulated responsibilities. The article explains the resulting test failures and recommends incremental refactoring, integration or smoke tests, and verifying behavior through tests.

## Source excerpt

When I've got some free time I try to add new features to springmock. Lately, after adding some new stuff I realized that double definition parsing class has more than one responsibility (class parsing, naming, definition creation, etc). So I've decided it's time to refactor it and split responsibilities into dedicated classes. Once I did that and tests in the shared kernel started to pass I executed mvn verify just to be sure that everything was working and it wasn't... Read more