#endtoendtesting — Public Fediverse posts

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

https://dev.to/hongster85/unit-vs-integration-vs-e2e-testing-understand-in-3-minutes-4pin

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

https://dev.to/hongster85/unit-vs-integration-vs-e2e-testing-understand-in-3-minutes-4pin

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

https://dev.to/hongster85/unit-vs-integration-vs-e2e-testing-understand-in-3-minutes-4pin

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

https://dev.to/hongster85/unit-vs-integration-vs-e2e-testing-understand-in-3-minutes-4pin

@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.

@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.

@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.

@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.

@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.