We recently released the much-anticipated Eggplant Functional 18.2, which includes some truly exciting innovations.
Earlier this month, we released Eggplant Functional v18.1. This latest version introduces a variety of new features designed with speed and efficiency in mind, and to bring Eggplant Functional and Eggplant AI closer together. Read on to see what’s in store when you upgrade.
Selenium is a popular open source test automation tool for lots of reasons. You can get started with it quickly. It’s widely used, so knowing it can be a marketable skill. And, because it’s not that easy to use right out of the box, testers who become well-versed in Selenium can advance into lucrative framework development.
Recently, we released eggPlant Functional v17, which introduces a variety of productivity features. Heavily inspired by user requests, v17 contains a little something for everybody…
The cross-platform tester. We know that a lot of our customers use helper suites to organize their related test assets across platforms– and that working on several suites at once can get messy. That’s why we’ve added the option to view helper-suite assets within your main suite window. This is a favorite around the Boulder office, and a favourite in the London headquarters.
For a lot of testing tools, the question of AngularJS support is complicated. Depending on your source, you’ll get something between a no and a sort of; which is why I’m happy to give eggPlant Functional an unequivocal yes.
eggPlant Functional doesn’t need an AngularJS extension. For code-level tools, a new development framework requires a new test framework. However, because eggPlant Functional works by finding elements on the screen instead of in your code, there is absolutely no difference between testing AngularJS and any other web technology.
TestPlant released eggPlant v16.1 this month, and I’m writing to talk to you about my favorite of the marquee features: support for Gherkin, the language of the Cucumber BDD framework. (Cue the vegetable puns!) Throughout our internal beta and in our v16.1 webinars, I’ve heard some great questions about Gherkin and our implementation of it that I’d like to share here. (I will also unabashedly share my preoccupation with Pokémon Go.)