Oracle has entered into a definitive agreement to

Oracle has entered into a definitive agreement to

first_imgOracle has entered into a definitive agreement to acquire the continuous integration platform provider Wercker. Wercker enables organizations and development teams to reach CI and continuous delivery goals with microservices and Docker with its container-centric and cloud-native automation platform. According to Oracle, with Wercker the company can continue its mission of democratizing developer tooling for the modern cloud. “Oracle already offers differentiated, enterprise-class IaaS and PaaS for companies building and running Internet applications and cloud services,” Mark Cavage, vice president of product development at Oracle, said in a statement. “Wercker greatly enhances the Oracle portfolio with a compelling Docker-based automation product and will accelerate the productivity of developers, across the entire spectrum, from the enterprise to the open source community.”SnapLogic releases Iris to automate enterprise integrationThe self-service integration provider SnapLogic is releasing new technology that applies machine learning to enterprise integration. Iris is built with artificial intelligence and designed to automate repetitive development tasks and eliminate integration backlogs. “Digital transformation shouldn’t depend on manual labor,” said Gaurav Dhillon, founder and CEO of SnapLogic. “The ancient pharaohs built the pyramids with manual labor, but there’s a better way to manage business automation and analytics. Starting today, the smart way to integrate data, applications and things will be autonomous — blending the best of machine and human intelligence. The days of simply throwing more developers at the problem are coming to a close.”The company’s first Iris-based feature is the Integration Assistant, a recommendation engine for building data pipelines. dtSearch release features has generation and searchingdtSearch announced the release of the new dtSearch product line versions with hash value support. Hash values are numeric codes used in forensic-oriented search solutions. The new versions can generate hash values as part of the indexing process, and append the hash values as searchable meta data.Other features of the product line include: terabyte indexer and multithreaded searching, more than 25 search options and international language support, faceted search and other data classification options, document filers and supported data types, and federated searching. NodeSource introduces N|Solid for Alpine LinuxNodeSource announced the release of NodeSource N|Solid for Alpine Linux. This is the newest addition to NodeSource’s enterprise Node.js platform, and it makes it easier for teams using Docker containers with the Alpine Linux distribution.NodeSource N|Solid is a commercial version of the Node.js runtime. It comes with enhanced security, real-time visibility into application performance, and support for development, DevOps, and security teams who want to run and scale Node.js applications. More information on N|Solid for Alpine Linux can be found here.Ansible Container 0.9The Ansible Container team announced the 0.9 release of the Ansible Container project today, with new features and tighter integration roles with Kubernetes in OpenShift Origin and Red Hat OpenShift Container Platform.With this release, Ansible ditched the main.yml playbook and replaced it with a per-service list of roles in container.yml. Ansible also built brand new Kubernetes and OpenShift modules, which are already being used in Ansible Container. Additional features include: the elimination of Python dependency in target containers, more tools in the conductor container, a new “deploy” command, and Dockerfile to Ansible Container conversion.More information on this release can be found here.Amazon’s new tools for building Alexa skillsAmazon rolled out new tools to help developers build their Alexa skills. Amazon announced a new beta testing tool for Alexa skills. Now, developers can now invite users to test their Alexa skills and provide feedback before it is published. Amazon also announced the Alexa skill builder, which lets developers build natural interactive dialogs. It includes new features for slot filling, confirmations and other natural prompts. This tool is also available today in beta on the Amazon developer portal.last_img read more

Mobile has dramatically transformed the way consum

Mobile has dramatically transformed the way consum

first_imgMobile has dramatically transformed the way consumers live and work. As mobile technology has become more sophisticated, the expectations that consumers have for their experiences have risen greatly. In this new high-stakes world, producing a mobile application that delights customers is more important than ever. But when it comes to determining what constitutes a great app, it’s difficult to separate fact from fiction. Let’s take a moment to debunk five of the most common mobile testing myths.1. Looks are more important than features.First impressions matter. That’s why visual testing and user acceptance testing are important — but they’re not everything. You shouldn’t just focus your tests on the visual and design aspects of your application. Features need to be thoroughly tested as well – especially the workflows that are most important to the overall user experience. If you don’t deliver what users expect, and what the business requires, the look of your UI won’t make much difference. The eye-pleasing app you were working on will still be uninstalled – and good luck with winning consumers back when that happens.2. It’s okay to run your tests on a single device.There are ample reasons to run your tests on a variety of devices from day one. While in the process of developing your app, if you only run tests on a single Android smartphone tethered to your development machine, you will probably be missing important bugs that will only be surfaced on other devices. In the true spirit of agile, it’s important to identify bugs and fix them early, versus waiting until late in the development process to find issues. Form factor and platform are not the only variables you will have to keep in mind: it’s also important to test across multiple OS versions and device manufacturers to ensure the greatest device coverage.3. Having an in-house testing infrastructure and managing devices is easy.Maintaining an in-house infrastructure that is current and reliable is complicated and managing a fleet of devices is not easy. You may end up spending a lot of developer time and money to create something that does not meet your needs, and waste precious resources that could be better used elsewhere. Device management takes a lot of time and money because devices need to constantly be maintained and updated with the latest OS and application releases. If you are thinking of Android or iOS emulators/simulators, these also need to be maintained and upgraded, and simulators require Mac hardware. Cloud solutions for both real device and iOS and Android emulators/simulators are better options because the cloud vendor is responsible for updating the devices to the latest operating systems, and providing a highly scalable and available solution.4. Exploratory testing is all you needExploratory testing is an important component of your overall testing strategy because it can often identify important bugs quickly, but it’s not sufficient on its own. To be effective, exploratory testing requires testers be familiar with the application, typical behaviors of the target user, and a variety of test methods. However, relying completely on exploratory testing exposes you to the risk that a key feature may not be tested because of an oversight or mistake. Therefore, exploratory testing should always be matched with a set of pre-defined scripted tests that ensure the most important application feature sets and workflows are functioning as expected.5. Code coverage is the ultimate measure of qualityWhile code coverage is a good metric to track, it’s more important to track and ensure that the key features of your application and the most common workflows have tests associated with them. Often a combination of automated tests, exploratory testing, and beta testing will yield better and faster results than just focusing on code coverage. Your percentage of code coverage will not matter if a key feature is missed!last_img read more