Clarification on integration and E2E stage in a pipeline

This page summarizes the projects mentioned and recommended in the original post on /r/devops

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • automated-test-environment-for-aks-applications

    Framework to create Automated Test Environment using kind (Kubernetes in Docker) for testing Azure Kubernetes Service (AKS) based applications in CI (Continuous Integration) Pipeline (Azure DevOps)

    As for the integration test: those are "just" API calls which is pretty expected for integration tests: it "just" tests an API which might use some other back-end services. You test those one by one.

  • python-poetry-docker-example

    Discontinued Example of integrating Poetry with Docker leveraging multi-stage builds. [Moved to: https://github.com/michaeloliverx/python-poetry-docker-example] (by michael0liver)

    One of the fun things that doesn't get explained often is if you want to you can target one of the intermediate containers and run it instead of running through the entire build. This means your development, hot-reloading environment can be a container that's in your production Dockerfile and all you have to do is modify the target when you're running locally. One of the best examples of this that I've found is a Dockerfile by michael0liver for poetry and python. You can see it here but the link to the entire repo is here.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts