i have an easy question.
When i test my application with behat is it also necessary to write
unittest with phpunit or does behat all the jobs for me?
I am trying to start to develop with bdd.
Behat is for acceptance tests and phpunit is for unit (and functional)
tests. They cover different aspects of testing.
Acceptance tests are for validating that your user stories/use cases are
correct
Unit tests are for testing the individual modules as a single unit (i.e.,
mock any dependencies the modules have), ensuring functionality is as
expected
Functional tests are for testing that your modules are wired together and
that your application is functioning as expected, that all paths through
the application work as expected, etc.
Some say there is a fine line between Acceptance tests and Functional
tests, but Acceptance tests are meant to be written by non developers
(business analysts, QA, etc), and Behat's use of the Gherkin syntax aids in
providing that functionality.
Optimally, you should be using all three forms of testing.
> i have an easy question.
> When i test my application with behat is it also necessary to write
> unittest with phpunit or does behat all the jobs for me?
> I am trying to start to develop with bdd.
> Thanks.
> --
> If you want to report a vulnerability issue on symfony, please send it to
> security at symfony-project.com
> You received this message because you are subscribed to the Google
> Groups "Symfony2" group.
> To post to this group, send email to symfony2@googlegroups.com
> To unsubscribe from this group, send email to
> symfony2+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony2?hl=en
> Behat is for acceptance tests and phpunit is for unit (and functional)
> tests. They cover different aspects of testing.
> Acceptance tests are for validating that your user stories/use cases are
> correct
> Unit tests are for testing the individual modules as a single unit (i.e.,
> mock any dependencies the modules have), ensuring functionality is as
> expected
> Functional tests are for testing that your modules are wired together and
> that your application is functioning as expected, that all paths through
> the application work as expected, etc.
> Some say there is a fine line between Acceptance tests and Functional
> tests, but Acceptance tests are meant to be written by non developers
> (business analysts, QA, etc), and Behat's use of the Gherkin syntax aids in
> providing that functionality.
> Optimally, you should be using all three forms of testing.
> --mark
> On Tue, Jun 12, 2012 at 3:08 PM, Sören Martius <
> soeren.mart...@googlemail.com> wrote:
> > Hi folks,
> > i have an easy question.
> > When i test my application with behat is it also necessary to write
> > unittest with phpunit or does behat all the jobs for me?
> > I am trying to start to develop with bdd.
> > Thanks.
> > --
> > If you want to report a vulnerability issue on symfony, please send it to
> > security at symfony-project.com
> > You received this message because you are subscribed to the Google
> > Groups "Symfony2" group.
> > To post to this group, send email to symfony2@googlegroups.com
> > To unsubscribe from this group, send email to
> > symfony2+unsubscribe@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/symfony2?hl=en
> Is it correct that the most used and importand test is UnitTesting
> cause of testing all the business Logic(such as models)?
> I thought functional Tests are Tests like Selenium Tests , which
> emulates an browser and tests the correct functionality?
> On 13 Jun., 00:22, Mark Badolato <mbadol...@gmail.com> wrote:
> > Behat is for acceptance tests and phpunit is for unit (and functional)
> > tests. They cover different aspects of testing.
> > Acceptance tests are for validating that your user stories/use cases are
> > correct
> > Unit tests are for testing the individual modules as a single unit (i.e.,
> > mock any dependencies the modules have), ensuring functionality is as
> > expected
> > Functional tests are for testing that your modules are wired together and
> > that your application is functioning as expected, that all paths through
> > the application work as expected, etc.
> > Some say there is a fine line between Acceptance tests and Functional
> > tests, but Acceptance tests are meant to be written by non developers
> > (business analysts, QA, etc), and Behat's use of the Gherkin syntax aids in
> > providing that functionality.
> > Optimally, you should be using all three forms of testing.
> > --mark
> > On Tue, Jun 12, 2012 at 3:08 PM, Sören Martius <
> > soeren.mart...@googlemail.com> wrote:
> > > Hi folks,
> > > i have an easy question.
> > > When i test my application with behat is it also necessary to write
> > > unittest with phpunit or does behat all the jobs for me?
> > > I am trying to start to develop with bdd.
> > > Thanks.
> > > --
> > > If you want to report a vulnerability issue on symfony, please send it to
> > > security at symfony-project.com
> > > You received this message because you are subscribed to the Google
> > > Groups "Symfony2" group.
> > > To post to this group, send email to symfony2@googlegroups.com
> > > To unsubscribe from this group, send email to
> > > symfony2+unsubscribe@googlegroups.com
> > > For more options, visit this group at
> > >http://groups.google.com/group/symfony2?hl=en
