The annual Gartner Symposium/ITxpo in Barcelona, Spain, is a great pulse check for what's on the minds of CIOs in large companies (like banks, utilities, telcos, governments). It's not necessarily the place to see the absolute latest technology, but it is the place to see what organizational problems CIOs are trying to solve with technology, and what companies are rolling out next year.
In my last post, I described a test team structure that I've seen several companies (which I think are real thought leaders in testing) successfully implement over the last few months. Included in that structure is the sometimes controversial statement that scrum teams should have dedicated, professional testers; that is, we shouldn’t make developers responsible for all testing (though they should be responsible for white-box unit testing).
How should we structure our test team? This is probably the most common question I hear when talking to test leaders about what's on their minds.
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.
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.
We have just released a new whitepaper about how to set up a successful test automation project based on our experience of working with hundreds of companies to successfully deploy test automation
Test automation can deliver huge benefits in terms of time-to-market, quality, productivity, and auditability to almost any team creating or deploying software. For example, TestPlant has worked with a leading global news publisher to reduce their app update cycle from three weeks to two days, a major UK bank to reduce post-release defects by 65%, and one of the world’s top five retailers to double the number of apps they are delivering without increasing the size of their test team. These stories are not uncommon – test automation really has delivered amazing benefits to lots of companies.
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.)
eggPlant Functional v16.1 is now available! Upgrade or download it to try out the new features today.
The eggPlant Functional v16.1 release is packed with features and updates that make setup and scripting easy for enterprise test deployments. ‘What kind of good stuff is this?’ you ask. Let’s dig in to find out…
Some of you may have attended our “Getting Started with Performance Testing” webinar a couple of weeks ago. The event was such a success, we’re doing it again! For those of you who missed it, make sure to sign up for the next session here. In the meantime, I’ll give you a taste:
In this webinar, we will run through the basics of performance testing. For a lot of folks just introducing test automation into their company (or even those who are already doing functional test automation), performance and load testing can be daunting.
To help alleviate the stress and clarify some first steps, we decided to run this webinar to help break down the basics for getting started. Steps for getting started include planning and preparation, test architecture, constraints, test creation/ recording, execution, and results.