i would only mention splinter and selenium as a nice way to communicate
with browser
actually a not so nice way, because we have lots of fixes and
monkeypatches, not only to splinter but also for selenium


On 28 August 2013 11:44, Dmitrijs Milajevs <notifications@github.com> wrote:

> In content/articles/pytest-bdd.rst:
>
> > +
> > +In the beginning we found the RobotFramework to be an easy tool to start writing
> > +the functional tests. It has a freedom of scripting, a library with the bindings
> > +to selenium webdriver and a possibility to write code in Python.
> > +
> > +Later the lack of limitations became a reason the BDD was not used as intended.
> > +Feature descriptions became programmatic with the variables in the text files,
> > +overlapping the requirements, scripting actions after observing results (
> > +When-Then-When-Then sections).
> > +
> > +But the biggest problem was the setup of the test. The whole Given section was hard to reuse
> > +because of the complexity of the system domain.
> > +
> > +But there was also something what we have learned from it...
> > +
> > +Splinter
>
> it seemed to me that Splinter is a BBD framework. It would be nice to
> mention that splinter is *used* by other frameworks in the very beginning
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/paylogic/dev-portal/pull/2/files#r6029293>
> .
>



-- 
Anatoly Bubenkov
+31(6)19999803