Pactflow Feature Road-map

This is a high level view of our product road-map. Don’t like the order or want to see something else here? You can change that by voting or asking for a feature:

If you aren't able to do this publicly, please contact us at hello@pactflow.io and we'd be happy to chat.

All of our upcoming work flows through the following five stages: Backlog Analysis Planned Work In Progress Released.

Current work in progress

The following features are in progress, and will be released soon...

OAuth2 Support in Pactflow on-premises edition

https://github.com/pactflow/roadmap/issues/39

Support for read-only (guest) users

https://github.com/pactflow/roadmap/issues/41

Bi-directional contracts with Open API Specification (Q1 2021 - available in developer preview)

We're adding support for a new model of contract testing: allowing teams to generate contracts from consumers and providers, and integrating with Open API Specification (OAS/Swagger). Our goals with this new approach are to:

  1. Expand the breadth of technology we can support (e.g. OAS, GraphQL, Protobufs, API Gateways etc.)
  2. Reduce the time-to-value of contract testing
  3. Simplify the adoption and scaling of contract testing
  4. Expand the types of ways a contract may be generated or verified, and allow the use of BYO tools (e.g. record/replay or instrumentation approaches to creating contracts, or tools such Cypress, MSW, Mountebank, Wiremock, Hoverfly and other such mocking tools)
  5. Expand the roles that can contribute to contract testing (such as Testers)

The first release is now available in developer preview (docs) and we are currently seeking feedback from our customers.

Thinking about and seeking feedback on

Permission to set contract visibility based on team (May 2021)

We're adding a new permission to scope contract visibility to your team. This is useful in high security environments, and in use cases where you may involve third parties in a particular project, but don't want them to have visibility of your entire system.

See https://github.com/pactflow/roadmap/issues/35 for more detail.

Released

The following features have been released:

  • Authentication using Github (April 2019)
  • Authentication using API tokens (April 2019)
  • New user interface (April 2019)
  • Webhook management and testing UI (July 2019)
  • Webhook secrets management for passwords and API tokens (August 2019)
  • Federated authentication via SAML (September 2019)
  • Authentication using Google (September 2019)
  • Viewing interaction level verification results (September 2019)
  • Subscription self-service (October 2019)
  • Audit API (January 2020)
  • Terraform Provider (March 2020)
  • v3 support for JS (April 2020)
  • XML Support for JS (April 2020)
  • Binary payload support for JS (April 2020)
  • C++ DSL (Consumer) with v3 support, XML and binary payloads  (April 2020)
  • Pactflow Enterprise On Premise (April 2020)
  • User self-service (June 2020)
  • Hosted API Stubs (July 2020)
  • System Accounts (Sep 2020)
  • Teams Management & Role-based Access Control (Nov 2020)
  • Bi-directional contracts with Open API Specification (Feb 2021)
  • Viewing triggered webhooks and execution logs (Feb 2021)
  • Configurable API Token expiry (March 2021)
  • Set user notices on login (March 2021)
  • Set an application-wide banner/notice (April 2021)
  • Manage user and system preferences (April 2021)
  • Team based secrets, webhooks and CI users (May 2021)
  • Team Administrators  (June 2021)
arrow-up icon