• qaz
    link
    fedilink
    English
    2323 days ago

    Why not? Why doesn’t the programmer want to test a container?

    • davel [he/him]
      link
      fedilink
      English
      1723 days ago

      True. Nothing beats running your unit tests in the actual container image that will be run in production.

      • @[email protected]
        link
        fedilink
        English
        10
        edit-2
        23 days ago

        Race condition that only happens on the much faster production hardware: Allow me to introduce myself

        • davel [he/him]
          link
          fedilink
          English
          723 days ago

          Unit tests can’t win ’em all. That’s where things like integration tests, staging environments, and load testing come in.

          The final layer of protection is the deployment strategy, be it rolling, canary, or blue-geen.

      • Björn Tantau
        link
        fedilink
        423 days ago

        I mean, isn’t that kind of the point of containers? To basically have the same environment everywhere.

      • qaz
        link
        fedilink
        English
        523 days ago

        Yeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.

      • @[email protected]
        link
        fedilink
        121 days ago

        Unit tests? No matter where you run them, and normally this is done by CI in a prebuilt container image, so you don’t have to wait for “docker building”. Acceptance tests must be run in an environment as close to production as possible, but that’s definitely not a programmer’s job.