Skip to main content
Software Quality Assurance & Testing

Return to Question

deleted 4 characters in body
Source Link
Roberto de Toledo
Roberto de Toledo
  • 123
  • 1
  • 6

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Test Pyramid of Tests, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (it's specifically about micro services, but it's still a good reference, right?).

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Pyramid of Tests, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (it's specifically about micro services, but it's still a good reference, right?).

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Test Pyramid, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (it's specifically about micro services, but it's still a good reference, right?).

remove language
Source Link
c32hedge
c32hedge
  • 2.7k
  • 19
  • 39

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Pyramid of Tests, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (OK, it'sit's specifically about micro services, but it's still a damn good reference, right?).

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Pyramid of Tests, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (OK, it's specifically about micro services, but it's still a damn good reference, right?).

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Pyramid of Tests, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (it's specifically about micro services, but it's still a good reference, right?).

Tweeted twitter.com/StackSQA/status/981821750647377921
Source Link
Roberto de Toledo
Roberto de Toledo
  • 123
  • 1
  • 6

Tests in CI: Are API + Integration Tests the most suitable?

In my experience, automated GUI tests may take too long for a build of Jenkins (even parallelized) and may demand a lot of maintenance. On the other hand API + Integration tests are way faster, do not demand so much maintenance, can be very functional and test e2e (backend, APIs, database...).

So thinking of the Pyramid of Tests, keeping the majority of the tests Unit Tests and in order to have a more functional test in Continuous Integration... Is API + Integration testing the best option for tests in CI? What's your take and experience on that? Is there a 'consensus'?

This article on Techbeacon talks about the issues of GUI tests in CI. Functional Tests in the eShopOnContainers are API tests (OK, it's specifically about micro services, but it's still a damn good reference, right?).