home.social

#endtoendtesting — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #endtoendtesting, aggregated by home.social.

  1. The testing pyramid advocates for a balanced approach with many fast unit tests at the base, fewer integration tests in the middle, and a minimal set of end-to-end tests at the top to ensure reliable and efficient bug detection.

    #UnitTesting #IntegrationTesting #EndToEndTesting

    dev.to/hongster85/unit-vs-inte

  2. The testing pyramid advocates for a balanced approach with many fast unit tests at the base, fewer integration tests in the middle, and a minimal set of end-to-end tests at the top to ensure reliable and efficient bug detection.

    dev.to/hongster85/unit-vs-inte

  3. The testing pyramid advocates for a balanced approach with many fast unit tests at the base, fewer integration tests in the middle, and a minimal set of end-to-end tests at the top to ensure reliable and efficient bug detection.

    #UnitTesting #IntegrationTesting #EndToEndTesting

    dev.to/hongster85/unit-vs-inte

  4. The testing pyramid advocates for a balanced approach with many fast unit tests at the base, fewer integration tests in the middle, and a minimal set of end-to-end tests at the top to ensure reliable and efficient bug detection.

    #UnitTesting #IntegrationTesting #EndToEndTesting

    dev.to/hongster85/unit-vs-inte

  5. How to use Stripe Test Clocks with Playwright E2E tests to simulate subscription billing lifecycles in minutes, not months, with real code examples. hackernoon.com/no-more-ship-an #endtoendtesting

  6. How to use Stripe Test Clocks with Playwright E2E tests to simulate subscription billing lifecycles in minutes, not months, with real code examples. hackernoon.com/no-more-ship-an #endtoendtesting

  7. How to use Stripe Test Clocks with Playwright E2E tests to simulate subscription billing lifecycles in minutes, not months, with real code examples. hackernoon.com/no-more-ship-an #endtoendtesting

  8. How to use Stripe Test Clocks with Playwright E2E tests to simulate subscription billing lifecycles in minutes, not months, with real code examples. hackernoon.com/no-more-ship-an

  9. How to use Stripe Test Clocks with Playwright E2E tests to simulate subscription billing lifecycles in minutes, not months, with real code examples. hackernoon.com/no-more-ship-an #endtoendtesting

  10. @melix Been there!

    I recently revamped the #cipipeline of a service at work & managed to cut down the time by ~60%.

    The trick was to avoid #docker (dind) & reuse the already provisioned resources (ie the build container) while ensuring a #ReproducibleBuild: while docker was used for almost anything, turned out the only time we really needed docker was for consumer #ContractTesting & #EndtoEndTesting and w/ a bit of effort we could safely run most of the tests in the original container.

  11. @melix Been there!

    I recently revamped the #cipipeline of a service at work & managed to cut down the time by ~60%.

    The trick was to avoid #docker (dind) & reuse the already provisioned resources (ie the build container) while ensuring a #ReproducibleBuild: while docker was used for almost anything, turned out the only time we really needed docker was for consumer #ContractTesting & #EndtoEndTesting and w/ a bit of effort we could safely run most of the tests in the original container.

  12. @melix Been there!

    I recently revamped the #cipipeline of a service at work & managed to cut down the time by ~60%.

    The trick was to avoid #docker (dind) & reuse the already provisioned resources (ie the build container) while ensuring a #ReproducibleBuild: while docker was used for almost anything, turned out the only time we really needed docker was for consumer #ContractTesting & #EndtoEndTesting and w/ a bit of effort we could safely run most of the tests in the original container.

  13. @melix Been there!

    I recently revamped the #cipipeline of a service at work & managed to cut down the time by ~60%.

    The trick was to avoid #docker (dind) & reuse the already provisioned resources (ie the build container) while ensuring a #ReproducibleBuild: while docker was used for almost anything, turned out the only time we really needed docker was for consumer #ContractTesting & #EndtoEndTesting and w/ a bit of effort we could safely run most of the tests in the original container.

  14. @melix Been there!

    I recently revamped the #cipipeline of a service at work & managed to cut down the time by ~60%.

    The trick was to avoid #docker (dind) & reuse the already provisioned resources (ie the build container) while ensuring a #ReproducibleBuild: while docker was used for almost anything, turned out the only time we really needed docker was for consumer #ContractTesting & #EndtoEndTesting and w/ a bit of effort we could safely run most of the tests in the original container.

  15. This made my day. Playwright now has a UI mode together with a Watch mode. The only two things I was missing from Cypress. youtu.be/jF0yA-JLQW0

    #Playwright #EndToEndTesting

  16. This made my day. Playwright now has a UI mode together with a Watch mode. The only two things I was missing from Cypress. youtu.be/jF0yA-JLQW0

    #Playwright #EndToEndTesting

  17. This made my day. Playwright now has a UI mode together with a Watch mode. The only two things I was missing from Cypress. youtu.be/jF0yA-JLQW0

    #Playwright #EndToEndTesting

  18. This made my day. Playwright now has a UI mode together with a Watch mode. The only two things I was missing from Cypress. youtu.be/jF0yA-JLQW0

  19. This made my day. Playwright now has a UI mode together with a Watch mode. The only two things I was missing from Cypress. youtu.be/jF0yA-JLQW0

    #Playwright #EndToEndTesting

  20. So, investing time in #endToEndTesting the QR code scanner on the web site I work on already paid off: a broken version was released github.com/mebjas/html5-qrcode

    It compiles, but the scanner just does not recognize the QR code.

    This is caught in the test.

  21. So, investing time in #endToEndTesting the QR code scanner on the web site I work on already paid off: a broken version was released github.com/mebjas/html5-qrcode

    It compiles, but the scanner just does not recognize the QR code.

    This is caught in the test.

  22. So, investing time in #endToEndTesting the QR code scanner on the web site I work on already paid off: a broken version was released github.com/mebjas/html5-qrcode

    It compiles, but the scanner just does not recognize the QR code.

    This is caught in the test.

  23. So, investing time in #endToEndTesting the QR code scanner on the web site I work on already paid off: a broken version was released github.com/mebjas/html5-qrcode

    It compiles, but the scanner just does not recognize the QR code.

    This is caught in the test.

  24. So, investing time in #endToEndTesting the QR code scanner on the web site I work on already paid off: a broken version was released github.com/mebjas/html5-qrcode

    It compiles, but the scanner just does not recognize the QR code.

    This is caught in the test.