Systems | Development | Analytics | API | Testing

Today is an exciting today for us here at Tricentis! We’re introducing two brand new products: Test Automation for Salesforce and Test Management for Jira. We’re also releasing a major upgrade of NeoLoad for performance testing. Together, these new releases will enable customers to deliver new capabilities and workflows to their business faster, collaborate more efficiently among product teams, and enhance digital experiences for all end users.

Chris Tozzi reviews the most popular JavaScript test automation frameworks and presents several things to consider as you select the best option for you and your organization. JavaScript consistently ranks as the world’s most popular programming language among developers. It should come as no surprise then that a variety of JavaScript test automation frameworks are available to help developers test JavaScript apps.

Developing applications in Linx follows common programming paradigms. This means that it will use variables, loops and if statements in a similar fashion to a traditional programming language. With this in mind, a recent update (6.4.1) introduced the Return function. The Return function is the new standard for returning values to the result of a function or to exit a function at any point. This post will go over what the Return function does and how it can be used.

This guide will take you through the steps to build and host an API using Linx. It will cover building a straightforward API to retrieve product data. You will be provided with the data, instructions for what tools to use, relevant scripts and all steps to get the API live. It will take about 20 to 30 minutes to complete all steps.

To be a leader in any industry is to be a leader in technology. In the whirlwind of digital transformation, innovation happens every day with software and software quality at the forefront. To not be left behind, now more than ever, CEOs, team leaders, and decision-makers should rethink software quality - the single most important element that determines their success.

There are a number of things to consider when automating your mobile app tests, but first and foremost is to decide which tests should be and can be automated. This means understanding the business goals that are most important to your organization, as well as the risks you want to manage and mitigate. Mobile app testing is ultimately about managing risk, and the only way to do that is to align testing practices with the most critical business processes and goals you need to cover.

There is an understated art to building good APIs – ones that are easy to integrate with, have high operational availability, offer readily attainable performance insights, and are easy to maintain. But if you have ever had to build an API from scratch, there is no denying that it is hard – and it gets much more complicated when you aim to deliver a quality API.

Testing is the bottleneck of devops. 80% of testing is done manually. This is time-consuming, error-prone, tedious, and expensive. It's a hundred times more expensive to fix an error caught in production versus an error caught. Dev teams are being pushed to release code faster, release new features faster, and beat their competitors in every possible way. Automation is a cheaper and more accurate way to test. It lets everyone focus on most important goals.