For many organizations, DevOps and Continuous Delivery are difficult practices to utilize. It is a challenge taken on by companies as a whole for the purpose of success and advancement.
Test automation is a long journey. Why go on it alone? Get out of your comfort zone and find out if TestArchitect is the perfect test automation tool for you. These are some reasons you should give TestArchitect a chance and schedule a demo today!
The Benefits of Automation Testing for Voice First Devices
Amazon Echo and Google home are both vying for control of your smart home. Both of these platforms are ushering in an era where voice first devices will become as ubiquitous as the smart phone is today. Amazon Alexa Voice Service, the technology that powers the Echo family of devices is already boasting over 10,000 skills or functions that can augment the usefulness or entertainment value of the platform, and more are being added all the time by third parties. Amazon is even licensing this technology to be built into third party devices like Sonos Speakers and Ford’s Sync car entertainment system. The need for testing of these custom skills and devices will be become more common place in the future like how mobile app testing is today. There is a unique challenge involved when testing voice first devices. Continue reading “The Benefits of Automation Testing for Voice First Devices”
A long time ago…
If we go back in time, to about 120 years ago, people were riding around in horse wagons or carriages. Then suddenly, the horse were gone and replaced by an engine and a steering wheel. But all in all, it still looked like carriage. A horseless carriage, to be more specific.
An important but often underestimated part of software development is testing. Testing is, by definition, challenging. If bugs were easy to find, they wouldn’t be there in the first place (although it should be noted that early in the SLDC various trivial bugs might show up as well of course). A tester has to think outside the box to find the bugs that others have missed. In many cases, understanding the business domain of an application is more crucial for effective testing, as is detailed knowledge of the application itself.