I went back to work on an old project that used Firebase's 2.4.2 library (as of this writing the newest library is 3.X, and there are some big changes between the two libraries. The key is that even though the syntax between the libraries is a little different, the underlying concepts are how you decide to use Firebase for your specific application are the same.
I seriously love using protractor-cucumber-framework, but it can be quite annoying trying to configure it perfectly, especially when you're doing it for the first time. I was having some trouble setting it up with my recent project, and decided to write a post about this specific error that I seem to run into often (hopefully that'll change soon! hehe) when adding this to my projects.
This is a very theoretical blog post on how to use Karma and Protractor in a BDD fashion.
Cucumber is a fantastic tool for writing automated BDD tests in the Gherkin language. Similar to unit testing and e2e testing, Cucumber builds on them to give you another level of testing- this one much easier for other team members to read and understand. I began this blog post soon after venturing off to implement cucumber.js into my project. Let's just say I didn't go down the absolute best path (hehe), and so this guide is really not the recommended way to use cucumber.js in an AngularJS application. If you're interested in doing it right, check out Setting Up Protractor to Run The Cucumber.js Testing Framework. If you are just curious what's so bad about this way and why it's "wrong" then keep reading! :)
The posts on this site are written and maintained by Jim Lynch. About Jim...