In July of this year Cruise, General Motor Co’s self-driving unit, delayed the commercial deployment of cars past its target date of 2019 as the vehicles required more testing before they could be safely on the road. In a blog post on the news Dan Ammann, Cruise’s CEO, wrote, “When you’re working on the large scale deployment of mission critical safety systems, the mindset of ‘move fast and break things’ certainly doesn’t cut it.”
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.
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.
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.