Shaping up for 2018 – five predictions for the software testing industry

With 2017 nearly over, organizations are hotly anticipating what the new year will bring in terms of trends, developments and hidden surprises in the software testing industry. For the software testing industry, it’s been a busy year. Increased automation adoption within testing teams – where agile development boosted speed of release – has led to QA becoming more embedded within development teams than ever before. As software testing and monitoring gains increasing importance, it’s time to ask – what’s next? Here are my 2018 predictions for our industry: Bigger AI breakthroughs Next year, we’ll see businesses really make breakthroughs when it comes to utilizing artificial intelligence (AI) and machine learning – namely to better understand captured data. It can be difficult to see how wider concepts such as AI manifest physically – intelligent objects or ‘things’ bridge that gap. In the past, connected devices sent data for limited processing; today, machine learning enables devices to transform that data into tangible insight, transforming the behavior of IoT devices worldwide. UX monitoring will be key With 2017’s major outages in mind, it’s clear the industry has not progressed quickly enough to address exponential IoT and API economy growth. Although some businesses are achieving great things in testing and monitoring terms, many organizations are still focusing efforts on speed instead of quality, security and resilience. Looking ahead to the new year, companies need to address the overall quality of their services to remain competitive. Consequently, we’ll see a shift in focus to monitoring the customer experience, as well as the need for thorough end-to-end testing, embedded within the delivery lifecycle. Differentiation will come down to availability If 2018 sees vendors offering similar capabilities, how will consumers decide where to spend their money? Differentiation of services will come down to availability, ease of use and a consistent, high quality experience. Increased reliance on IoT devices, their data and their management will also drive the need for high availability of the API services that these devices interact with. Monitoring availability of these APIs is key to ensuring that organizations can run – especially in the manufacturing space – and that business intelligence data can be trusted by leaders. The CMO role will evolve Historically, software testing and monitoring has been the responsibility of the IT department, be that the development teams for testing, or operations on the monitoring side. Next year, with digital transformation underway in most organizations, in addition the explosion of connected devices and data processing derived from IoT, focus will shift onto application quality as well as customer experience. Thus, testing and monitoring should be of keen interest to the COO and the CMO: this will result in more rounded testing with team members coming from different parts of the organization. That’s a potential step change in the type of testing that would occur. Validation of results will transform In 2018, we will see further adoption of AI: major software vendors will increasingly embed machine learning within their core applications.  In addition, machine learning will become a standard platform for data analytics for new development initiatives – benefiting IoT vendors most of all, due to the explosion of data in the market. This will challenge the testing community as new ways of testing and validating the results from AI need to be identified. — Although I have confidence in these predictions, I’m aware that there will be events in the new year that no one in the industry could foresee. However, we at Apica look forward to the challenge. Here’s to a successful 2018!  

LoadRunner or JMeter: A False Premise

When I speak to QA Managers in my daily routine, I often hear a common scenario, they own LoadRunner as their performance load testing solution, but they have been told by “C” level executives within their organization to replace it with a “free” open source solution like JMeter. This is almost always due to the excessive price of LoadRunner’s annual renewal, coupled with the fact that every year it becomes more and more outdated and less relevant to the complex demands of today’s load testers. LoadRunner or JMeter? As LoadRunner’s deficiencies become more apparent the justification for keeping it becomes harder to justify price-conscious IT organizations, and rightly so. Here are the five major deficiencies LoadRunner customers tell me frustrates them: Windows only based architecture that lack support Apple and Linux OS’s. Scripts can only be created by complex programming (C++ & JavaScript) so testers with this know-how are both expensive and hard to find. Not DevOps friendly – limited or awkward support DevOps tools like Jenkins, JIRA, Bamboo, CodePipeline etc. API Support – APIs can only be created manually by complex & time-consuming programming. Server deployed – LoadRunner’s Lacks real-time test collaboration and unlimited scalability you see with SaaS-based load testing solutions. Given the high cost and lack of innovation of LoadRunner, it’s no wonder companies decide to make a 180-degree turn to open source tools. However, in many cases, this choice is moving from a difficult situation to a much worse one. JMeter brings its own set of challenges as a load testing solution: Like LoadRunner, it too requires users to know complex programming to create scripts. Open source tools cannot offer tech support, so you need to search the internet for answers which may or may not be helpful and can be time-consuming. It’s not secure. How many trojan horses have hacker left in the open source code? I don’t know and neither does anyone else. Your security officer will probably not be happy with an open source tool either. Also like LoadRunner it does not scale well when pushed to today’s large or even mega tests, that many organizations now require. Free? – There are many costs associated with open source software. The costs associated with the lack of the ongoing maintenance and support as well as the creating news scripts– not to mention the security risk. As a sales professional, I use Salesforce. I use it because it is simply the best CRM solution on the market in my experience. Yes, it cost my company money, and yes there are many open source tools that I could use. But as a professional, I have decided to give myself the best chance at success. My management is not going to congratulate me if I miss my sales goals but saved the company money by using an open source CRM.  That’s not how the world works. LoadRunner or JMeter is a false choice. There is a third alternative, Apica LoadTest. Apica LoadTest offers a modern alternative with modern capabilities: Advanced Scripting Engine – Create realistic and complex load test scripts without programming, plus it runs Selenium, LoadRunner, and JMeter scripts. OS Support – Windows, Linux, and Apple. Modern deployment options – SaaS, On-Premise, or Hybrid. Unmatched scalability – Up to Tens of million concurrent virtual users. API Test – Chaining together complex API calls without programming. Agile DevOps support – Jenkins, Bamboo, Git, AWS Team City, CodePipeline and more. Native APM Integrations – AppDynamics, Dynatrace, New Relic. Multi-Team Support – Real-time, centralized, better collaboration and superior testing. 24/7/365 GLOBAL SUPPORT – All performed in-house. Secure – WillRead More