Yupp, you’ve guessed it, HTTP. HyperText Transfer Protocol (HTTP/HTTPS) is the go-to language for IoT devices, in that it’s the protocol used when devices talk to each other via the internet. I know what you are thinking: what about everything we’ve heard about security in the news? Surely there is nothing more important than security in IoT? Security was a close second for me when deciding the most important thing about testing, but here’s why HTTP pipped it to the finish line…
We operate in a continuous delivery world in which a seamless customer experience is paramount. Regardless of whether you’re a global Fortune 500 organization or a fast-growing startup, failing to deliver a digital experience that delights your users is a critical mistake you can’t afford to make.
There are certain inalienable truths about businesses: they all want to succeed and they all want to beat their competitors. What's slightly different is how a business defines success. For a healthcare company, it might be lives saved. For an insurance company, it's the number of policies bought. For an e-commerce retailer, it's shopping basket conversions.
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.
Sometimes I feel as if I’m the Forrest Gump of quality assurance (QA). Since 1998, I’ve been through the beginning of automated integration testing and service virtualization through being a co-founder of Class I.Q. (now IBM Greenhat). I’ve been through the first phases of an automated testing center of excellence (ACOE). I’ve been there for the start of risk-based testing, and I’ve been a part of the transformation of QA from a somewhat necessary function to something that is now the core and chief concern of any company putting out quality software and apps.
We recently co-hosted a webinar with Bloor Research about the Future of Testing, and in it, we conducted an informal poll about artificial intelligence (AI) and testing. When we asked what everyone thought the biggest advantage was to incorporating AI into a test automation strategy, attendees overwhelmingly selected team productivity and efficiency.
One of the challenges in setting up tests with Selenium WebDriver is determining the best locator for an element. Eggplant Functional and SenseTalk provide several ways to locate elements. The Selenium community recommends CSS Selector as the best method for locating elements. It's powerful in that it can identify elements based on classes, identifiers, where they fall in the DOM hierarchy, etc.
The focus on artificial intelligence (AI) in general, in technology, and particularly in testing, is prompting organizations worldwide to take it seriously. It’s hard to ignore AI’s potential benefits, including improved productivity and efficiency, fewer defects, a better UX, and happy customers. And with DevOps and continuous delivery here to stay, staying relevant depends on keeping pace, which is why test automation is so critical.
To fully automate the execution of Selenium WebDriver tests through Eggplant Functional, it’s convenient to set up the Selenium Standalone Server to run automatically every time the system under test boots. If the Standalone Server isn't running, the test will not execute, leading to delays in continuous integration, and false-negatives on regression testing.