Functional tests, as you would with Cucumber, are very different from unit tests. A unit test should test the unit of work at the method / class level. They ideally should not check the interaction between the entire system. They must be fast and isolated (see http://agileinaflash.blogspot.com/2009/02/first.html )
Thats where Cucumber comes in. It provides a front where customers can help determine what they want to do, and then you write tests that implement it. This means that the cucumber layer is most likely at the same level as the user interface (and thus does not allow placing logic in the user interface as a bonus).
, , , ( ), . CI, .