Our shiny new XPath XML data assertion is capable of extracting values from XML and HTML documents and comparing the value to hard-coded data and dynamic variables. This functionality opens up a lot of new ways to automate tests for your API or website.
Testing and monitoring web services in production (TiP and MiP) helps software and testing teams improve overall quality and gain a better understanding of how systems behave with real users and requests. These are few reasons why you should be testing and monitoring in production.
Many API and website testing scenarios require chaining HTTP requests and setting up pre-requisite data fixtures to validate an endpoint's payload or status code. To support these workflows, we are excited to roll out our most requested feature - multiple setup steps - which can be used to chain HTTP requests and populate dynamic test data.
We're thrilled to release a new feature for configurable rate limiting on web services in Assertible. This allows you to more closely model your real-world services by throttling how fast HTTP requests will hit your API or web app.
Behind every great API is a reliable uptime monitoring system. In today's internet world filled with SaaS apps, there are many monitoring tools to choose from. In this post I'll outline some tips to help you determine what and how to monitor your API. Using these tips can help you build out API monitoring automation that works well for your needs.
Assertible and Postman are both great tools that with many benefits for testing and monitoring APIs. In this post, I'll illustrate a few important advantages that make Assertible a great choice for teams looking to choose an automated testing tool.
Environment variables, the newest addition to Assertible, make it easier and faster to write reliable tests using static data fixtures, no matter where your web service is deployed.
At Assertible, we're creating a platform that helps you test and monitor APIs and websites. A big part of this is being able to model real-world use-cases. Today, we're happy to anounce that teardown steps are now available for all users.
In this post I will outline why Assertible is a good fit for teams to test APIs and illustrate precisely how Assertible improves on features that both Assertible and Runscope offer.
Running your API tests across different environments, like staging, qa, and production, helps ensure the uptime and available of your web services. The new environment level authentication in Assertible gives you more control over testing your application on different URLs.
We're constantly looking for new ways to make testing your web service easier by finding patterns in how HTTP requests are created and tested. The new enable/disable option for request headers and parameters will help you create and iterate on more tests for a wide range of use-cases.
As APIs continue to become an integral part of how business and developers work, the API community is flourishing with new tools and solutions that make working with and testing these systems easier. In this post, you'll learn about 10 API testing tools to keep your eye on in 2017.
As you create new tests for your web app and push new features to production, you'll want to run your tests on a schedule to continuously validate your web services. These new schedule features will help you improve your web service monitoring.
Recently, there was a brief outage in one of the APIs we monitor with both Assertible and Pingdom, SimplyRETS. Our whole development team was away from the keyboard when this problem happened which sparked a conversation regarding just how important effective alerts and notifications are in an API monitoring tool.
Ever wondered what the difference is between GET and POST requests, or when to use PUT? You're not alone. In this post (no pun intended), I'll give you a breakdown of each method and what you need to know when testing APIs.
In this post I'll illustrate how to run API integration tests during a CI build as part of a continuous testing strategy. The goal is to validate that the API or web application performs as expected under production-like circumstances. This strategy can be used to verify an app's functionality before a deployment or other parts of a continuous delivery processes.
We are happy to announce two major improvements to our Trigger URLs. You can now run your tests against any dynamic URL and fail your continuous integration build or script when tests fail. These improvements make it possible to execute API tests in a continuous integration & delivery pipeline against any host.
AWS's API Gateway is a great tool that makes it easy for developers to create and publish an API. In this post, I'll show you how to set up automated API testing and monitoring for all of your endpoints.
We're excited to release two new improvements to the dashboard: a new test list view helps you find and manage API test failures, and the deployments history now links directly to the test result for that deploy.
In this post I'll describe how to automate API tests defined in a Postman Collection from a continuous integration or delivery pipeline using Assertible.
I am happy to announce that Assertible now supports importing and automating API tests from Postman Collections. Postman has become a powerful developer tool for exploring and defining reusable API or website tests using the Postman Collections format.
We have released a new NPM package called move-file-loader. This module is a loader for Webpack to move files from one location to another during compile time.
Testing your API or web app after deploying from a CI pipeline helps catch bugs earlier and faster in the development process. This post explains how you can test your API from a Jenkins build step using Assertible.
In this post, I will illustrate 3 simple examples for testing an HTML website using Assertible. The examples described in this post are perfect for continuously smoke-testing your site from a continuous integration pipeline or deploy script.
Learn how to run post deploy smoke tests against your API or website from any Codeship pipeline.
With the Zapier integration for Assertible, you can automatically open an issue on any GitHub repository when API tests are failing. This post will show you how to set it up.
This post illustrates 3 simple examples for testing a JSON API using Assertible. These examples assume you have an Assertible account and a test created.
How to continuously test an API using a Swagger / OpenAPI definition from a continuous integration or delivery pipeline.
In an ideal world, every continuous delivery pipeline would incorporate automated functional testing. Even if you are not automating deployments directly to production, there are several distinct advantages to automatically running integration, acceptance, and end-to-end tests against every release of your application immediately after it's deployed.
Test your web app across any environment, like staging or production, and use these new dashboard features to instantly view the results and status of your tests.
The new and improved deployments API is capable of integrating with GitHub and your continuous delivery pipeline so you can monitor your web service deployments and test failures directly from GitHub pull requests and other commit references.
Learn how to set up an automated API testing and monitoring pipeline based on a Swagger or OpenAPI specification
Learn how to set up automated smoke tests and monitoring for your web services using Assertible in 5 minutes.
We have overhauled our GitHub integration to require less permissions for access to your resources. Unless you are using the GitHub deployments integration, Assertible only requires access to your email.
A step-by-step guide for automatically smoke testing a Go application every time it's deployed to Heroku.
Integrate Heroku Review Apps and Assertible to create turn-key automated QA pipelines for web applications. Test results are propogated to GitHub status checks making it trivial to identify failures from pull requests.
Validate all JSON endpoints for your web service using JSON Schema Draft 4.
Use these 4 essential techniques to build reliable API and web service test automation for your QA pipeline.
View your web service deployment history and easily make powerful JSON assertions without writing code.
Assertible supports running automated web service tests against different environments from the dashboard, and supports a new environment parameter on API status badges.
The best time to run API tests is immediately after a deployment. Use Assertible deployments to continuously test your web app.
Introducing new metrics for testing and monitoring your web services.
Learn how to set up a continuous integration, deployment, and testing pipeline for a Node.js app using CircleCI, Heroku, and Assertible.
Assertible's new via property for test results makes it trivial to instantly view where a test result originated.
Assertible's new Zapier integration allows you to instantly send data about your API test result to other services, opening up more ways to automate your API testing.
Common deployment failures can be quickly detected and often prevented by automating end-to-end acceptance testing as part of the continuous integration process.
API failures are inevitable; the important part is how quickly you can react. Here are 4 common API failures, and how you can test them.
Learn how to test APIs behind a firewall using `ngrok` and Assertible.
Using setup steps to capture variables and parameterize HTTP requests allows you to test a wide range of use-cases for your web service.
At Assertible, we automatically run tests against our APIs after every deployment to reduce bugs, validate functionality, and save developer time.
Instantly view GitHub pull request status checks for your Assertible post-deployment tests.
This package provides a function to be run on AWS Lambda that sends CloudWatch notifications to your Slack channel.
A good continuous development workflow makes developers more productive by providing constant feedback during the build, deploy, and test cycle. These 5 services will complete your CI pipeline.
This post discusses and provides code samples for how we use React components to create our email templates.
Running automated QA tests against your web service every time you deploy to Heroku is the best way to complete your continuous integration pipeline. Using Heroku Review Apps along with our GitHub deployment integration makes this trivial using Assertible.
The Assertible GitHub integration makes it easy to automate your QA pipeline by running post deployment API tests every time you deploy your web application.
Assertible's simplified assertions allow you run known-to-be-valuable tests against your live web service
The easiest way to test and
monitor your web services
Reduce bugs in web applications by using Assertible to create an automated QA pipeline that helps you catch failures & ship code faster.Get started with GitHubSign up for free
New feature: multiple setup steps 07/19/2017