Java EE and MicroProfile testing survey

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Terminology: In this survey, an "application" refers to a single deployment artifact. For example, a jar, war, ear, Docker container, or similar.

On average, how many automated test cases do you have for a single application? *

1-20

21-100

101-1000

More than 1000

On average, how long does it take to run all of your automated tests for a typical code change? This should only include how long it takes tests to execute, not build or deployment. *

Less than 1 minute

1-5 minutes

5-15 minutes

15-45 minutes

More than 45 minutes

Approximately what percentage of the total build/test/deployment pipeline duration is consumed by running automated tests? *

Less than 33%

33-66%

More than 66%

On a scale of 1-10, what level of confidence do you have that your existing automated tests will identify a functional regression? *

Not confident

Most confident

If you selected less than a 10 for confidence in your automated tests, what factors are causing this? Select all that apply.

Debugging a test that fails is too time consuming, so we don't run as many tests as we would like to

Our application is too big/complex to write automated tests for

Running the tests we do have takes too long, so we don't run as many tests as we would like to

Setting up or configuring automated tests on a new project or new machine is too complicated

Writing tests is too complicated or time consuming compared to the benefit they provide

The tests we have do not accurately represent how our application runs in production. Even though a test may pass, the application may fail because it behaves differently in production.

Other:

Which type of tests contribute more to your confidence in your automated tests? *

Unit/mock tests

Integration testing (i.e. "live server" tests)

Relative to other aspects of creating and maintaining an application, how easy or difficult is the process of writing new automated tests? *

Writing new tests is one of the easier parts

Writing new tests is not significantly easier or harder than other parts of the development process

Writing new tests is one of the hardest parts

We don't have any automated tests

For overall application maintenance, what percentage of time is spent debugging or fixing test issues? As opposed to true application bugs.

0% (we don't have any automated tests)

Less than 33%

between 33 and 66%

more than 66%

Clear selection

What aspects of your application do you find significant difficulty in testing? Select all that apply. *

Code that depends on system/env variables

Our non-prod environments are too unstable (data is frequently changed, services overloaded, or services are down)

Code that works with messaging (e.g. Kafka or MQ)

Code that communicates with databases

Code that communicates with external HTTP endpoints

Procedures that are self-contained to the application and do not rely on any external services

Code that communicates with an external authentication service

Other:

Required

Do your applications run in Docker in dev, test, or production environments? *

Yes

What's Docker?

What tools/libraries do you use for automated testing? Select all that apply. *

JUnit 4 or older

JUnit 5 / JUnit Jupiter

TestNG

Mockito, EasyMock, or other mocking frameworks

Arquillian

Testcontainers

Selenium

Other:

Required

If you have any additional comments on any of the above questions, or want to voice any pain points that were not covered by the survey, please include them below.

Submit

Clear form

Never submit passwords through Google Forms.

This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy

Forms