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 past weekend my uncle Keith came up from Virginia. He's a Chiropractor, and while he was here he adjusted me. Afterwards, I realized that what he was doing was very similar to software testing!
Here's a post I wrote after having an "aha moment" about how to efficiently keep my living documentation up-to-date and easily accessible. Enjoy!
This is a very theoretical blog post on how to use Karma and Protractor in a BDD fashion.
Good old BASH is probably the most popular command shell out there. Take any randomly selected Angular or React developer and ask him or her what type of computer OS they use, 99% of them will say Mac OS. Why? Some will tell you they like the sleek interface of Mac or it's resilience against malware, but the real key comes down to having a BASH shell. This is huge because things like npm, gulp, ng cli, ssh, git, travis CI, karma, protractor, cucumberjs, and more all run in a BASH shell. Sure, Windows has it's own command line, but it's not the same. Not at all! Lol. Anyway, I'm super excited that Windows has managed to give their own command line support for BASH, unlocking otherwise difficult to take on projects for many developers including my friend Wayne Pao who is fearlessly learning test automation with AngularJS right now as I'm typing this now (on his windows machine)!
The posts on this site are written and maintained by Jim Lynch. About Jim...