Allows you to run a block of assertions as long as a condition is valid.
Parameters:
| Name | Type/Value | Required |
|---|---|---|
| Expression | Expression | Yes |
Expression: The condition that has to be met for the assertions block to be executed
Documentation for the API Fortress platform.
- Assertions for Metrics / Performance
- Automating 3-Legged OAuth
- Build an Integration Test (Multistep Test)
- Copy a Test
- Dealing with Authentication (Simple, oAuth, etc)
- Different ways to compose a Request Body
- Disable SSL Validation
- Dynamic dates
- Executing from Cucumber
- Following redirects
- Footprint
- Generate a Status Page
- Generating Fake Test Data
- GitHub – How to Use Files as Datasource (Large or Small Datasets)
- How to create a dynamic header
- Import / Export Tests
- Key/Value Store
- Load Agent Deployment (On-Premises)
- Setup Notifications (Performance Alerts)
- Testing GraphQL
- Update Input
- Use Long Lasting Tokens
- Using the Local Engine (APIF-Local)
- Version Control
- Write Tests in Code
- Add New Connector
- Alert Thresholds (Using JSON Connector)
- Bamboo – Integrate API Tests & Results
- Build from Apiary
- Build from Axway
- Build from Mashery
- Connectors – BigPanda
- Connectors – DataDog
- Connectors – Hipchat
- Connectors – JIRA
- Connectors – PagerDuty
- Connectors – Slack
- Connectors – StatusPage
- Helper – Connect to Any Database
- Helper – Connect To Files
- Integrate with Test Modeller (Curiosity Software)
- Jenkins – Tricentis qTest Integration
- Jenkins – Zephyr Enterprise Integration
- Single sign-on with SAML 2.0 (beta)
- Version Control
- 11. Using Variables for Environment Flexibility
-
12. Environments, Vault,
and Variable Overrides - Data Manipulation Tricks (Random Numbers & Strings)
- Improving Your Metrics
- Input Sets and Global Variables
- Outline a Plan For Your Test
- The Working Copy / Published Tests
- Using Test State Variables
- Working With the Header (status code, latency, fetch)
- Backing Up Your Data – Kubernetes (On-Premises)
- Backing Up Your Data (On-Premises)
- Best Practices for Disaster Recovery (On-Premises)
- Deployment – Configure the DNS for the Mocking service
- Deployment – Docker (On-Premises)
- Deployment – Kubernetes (On-Premises)
- Deployment – Red Hat OpenShift (On-Premises)
- Enabling API Fortress to Read Local Files
- Load Agent Deployment (On-Premises)
- Local Downloader Setup (On-Premises)
- On-Premises System Requirements
- The On-Premises Platform
- Updating an On-Premises Instance
- Updating the API Fortress License Key
- Assert Compares
- Assert Contains
- Assert Equals
- Assert Exists
- Assert Greater
- Assert In
- Assert Is
- Assert Less
- Assert Matches
- Comment
- Company settings
- Composer Snippets
- Connecting to TestRail
- Databases – JDBC (direct)
- Delete
- Each
- Execution Context in API Fortress
- Expression
- Expression language extensions
- Flow
- Generating a JWT
- Get
- GitHub – Use a File as a Datasource
- I/O Operations
- If
- Key/Value Store
- Main dashboard
- Patch
- Post
- Project dashboard
- Put
- Read File (On-Premises Only)
- Set
- Tag
- Test Control Panel
- Update Input
- While
API Testing University