Eggplant Blog

Though we may have grown accustomed to transitioning over to a more digitized way of living over the last couple of weeks, it’s safe to say that our new normal will indeed be changed forever. More of us have opted into making purchases online, with many retailers suffering from a decrease in footfall as we all do our best to stay safe.   

To provide the best possible patient care, hospitals need to ensure that the EMR is working properly after every change. While the EMR itself is a critical link in overall patient management, ensuring seamless connectivity across numerous other hospital systems (ERP software, PACS technology, blood bank software) is also important. This means end-to-end testing of software releases, updates, functionality, and performance — not just testing that the code works in one system or another.  

TestPlant CTO, Antony Edwards, was interviewed by Mobile World Live at Mobile World Congress in Barcelona this year. Antony talks about the key trends in mobile and IoT, and how testing needs to change in order to be more focused on UX. 

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.)

A lack of environment management is one of the most common reasons for unreliable test execution. People remove devices from the test environment, change app versions without notification, change OS settings, two tests try to use the same devices at the same time, a manual tries to use the same device at the same time, a backup runs on the middle of a test run, insufficient user data is provided, and the list goes on.