Some of my customers are trying to design an automated script to perform specific workflows with a predicted outcome. Unfortunately, the automated workflow they want to execute has many variations in their environment, and they’re having trouble creating a dynamic, automated script that handles environment deviation.
Note: Test engineer Reena Kuni and software engineer Bekki Freeman also contributed to this blog.
On the Eggplant Functional team, the relationship between Dev and QA is very collaborative. We work closely together, use our Slack channel to organize regular walk breaks together, and frequently talk about ways to increase product quality.
Note: Test engineers Reena Kuni and Jeannette Smith also contributed to this blog.
This blog is only partially about our newest iOS Gateway 5.0 release with device and simulator support for Touch ID and Face ID (which is super cool, but more about that later). It’s also a blog about how testing has changed — a lot — in a short amount of time.
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.