Test profiles and configuration in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of test profiles in Spring Boot?

Test profiles in Spring Boot allow you to define different configurations specifically for testing environments. This helps isolate test settings from production or development settings, making tests more reliable and easier to manage.

beginner

How do you activate a test profile in Spring Boot?

You activate a test profile by setting the spring.profiles.active property to the desired profile name, either in application.properties, application.yml, or as a command-line argument when running tests.

intermediate

What is the role of @ActiveProfiles annotation in Spring Boot tests?

The @ActiveProfiles annotation tells Spring Boot which profile(s) to use when running a test class. This ensures the test loads the correct configuration for that profile.

intermediate

How can you define different database configurations for tests using profiles?

You create separate configuration files like application-test.properties with test-specific database settings. When the test profile is active, Spring Boot loads these settings, allowing tests to use a test database instead of production.

beginner

Why is it important to separate test configuration from production configuration?

Separating test and production configurations prevents tests from accidentally affecting real data or services. It also allows tests to run faster and more predictably by using mock or in-memory resources.

Which annotation is used to specify active profiles in a Spring Boot test?

A @TestProfile

B @ActiveProfiles

C @ProfileTest

D @EnableProfiles

The @ActiveProfiles annotation is the correct way to specify which profile(s) to activate during a Spring Boot test.

Where do you typically define profile-specific properties in Spring Boot?

A application-{profile}.properties or application-{profile}.yml

B test.properties only

C application.properties only

D pom.xml

Spring Boot loads profile-specific properties from files named application-{profile}.properties or application-{profile}.yml.

What happens if you do not specify a profile when running Spring Boot tests?

A Spring Boot randomly picks a profile

B Tests will fail to run

C Spring Boot uses the production profile

D Spring Boot uses the default profile

If no profile is specified, Spring Boot uses the default profile, which may not be suitable for tests.

How can you activate a test profile from the command line?

A Using --test.profile=active

B Using --profile=test

C Using --spring.profiles.active=test

D Using --activate.test.profile

You activate a profile by passing --spring.profiles.active=test as a command-line argument.

Why might you use an in-memory database in a test profile?

A To isolate tests and speed up execution

B To connect to production data

C To increase test complexity

D To disable database access

In-memory databases isolate tests from production data and run faster, making tests more reliable and efficient.

Explain how Spring Boot uses profiles to manage different configurations for testing and production.

Think about how you might switch settings like databases or API endpoints between test and real use.

Describe the steps to set up a test profile in Spring Boot and how to activate it for running tests.

Consider both configuration files and annotations.

Practice

1. What is the main purpose of using test profiles in a Spring Boot application?

easy

A. To run the application with special settings only during testing

B. To improve the application's runtime performance in production

C. To automatically generate test data for the application

D. To disable security features permanently

Solution

1. Step 1: Understand test profiles concept

   Test profiles allow running the app with different settings specifically for testing purposes.

2. Step 2: Compare options

   Only To run the application with special settings only during testing correctly describes the purpose of test profiles as special settings for tests.

3. Final Answer:

   To run the application with special settings only during testing -> Option A

4. Quick Check:

   Test profiles = special test settings [OK]

Hint: Test profiles isolate test settings from production [OK]

Common Mistakes:

• Confusing test profiles with performance tuning
• Thinking test profiles generate test data automatically
• Assuming test profiles disable security permanently

2. Which of the following is the correct way to name a properties file for a test profile named testdb?

easy

A. application.properties.testdb

B. testdb-application.properties

C. application-testdb.properties

D. application_testdb.properties

Solution

1. Step 1: Recall Spring Boot profile file naming

   Spring Boot uses the pattern application-{profile}.properties for profile-specific config files.

2. Step 2: Match the pattern with the profile name

   For profile testdb, the correct file name is application-testdb.properties.

3. Final Answer:

   application-testdb.properties -> Option C

4. Quick Check:

   Profile file = application-{profile}.properties [OK]

Hint: Use application-{profile}.properties naming [OK]

Common Mistakes:

• Placing profile name after .properties
• Using underscores instead of hyphens
• Reversing the order of profile and application

3. Given the following test class annotation:
@ActiveProfiles("test")
and two property files:
application.properties with db.url=prod-db
application-test.properties with db.url=test-db
What will be the value of db.url during this test?

medium

A. prod-db

B. test-db

C. null

D. application.properties

Solution

1. Step 1: Understand @ActiveProfiles effect

   @ActiveProfiles("test") activates the 'test' profile for the test run.

2. Step 2: Determine property file precedence

   Properties in application-test.properties override those in application.properties when 'test' profile is active.

3. Final Answer:

   test-db -> Option B

4. Quick Check:

   Active profile properties override default [OK]

Hint: Active profile properties override defaults [OK]

Common Mistakes:

• Assuming default properties always apply
• Confusing profile name in annotation
• Expecting null if profile is active

4. You have a test annotated with @ActiveProfiles("dev") but the test still uses properties from application.properties instead of application-dev.properties. What is the most likely cause?

medium

A. The test class must extend a special base class to use profiles

B. The @ActiveProfiles annotation is only for production

C. Spring Boot does not support multiple profiles

D. The application-dev.properties file is missing or misnamed

Solution

1. Step 1: Check profile file presence

   If application-dev.properties is missing or named incorrectly, Spring Boot falls back to application.properties.

2. Step 2: Verify annotation usage

   @ActiveProfiles works for tests to activate profiles; it is not limited to production.

3. Final Answer:

   The application-dev.properties file is missing or misnamed -> Option D

4. Quick Check:

   Missing profile file causes fallback to default [OK]

Hint: Check profile file name and location first [OK]

Common Mistakes:

• Thinking @ActiveProfiles is ignored in tests
• Believing Spring Boot lacks profile support
• Assuming inheritance is required for profiles

5. You want to run integration tests with a profile integration that uses a different database URL and disables security. Which combination correctly activates this profile and overrides the default settings?

hard

A. Create application-integration.properties with overrides and annotate tests with @ActiveProfiles("integration")

B. Add spring.profiles.active=integration only in application.properties

C. Use @Profile("integration") on the test class without any properties file

D. Set environment variable SPRING_PROFILE=integration but keep default properties unchanged

Solution

1. Step 1: Use profile-specific properties file

   Create application-integration.properties to override database URL and security settings for the integration profile.

2. Step 2: Activate profile in tests

   Annotate tests with @ActiveProfiles("integration") to activate the profile during test runs.

3. Final Answer:

   Create application-integration.properties with overrides and annotate tests with @ActiveProfiles("integration") -> Option A

4. Quick Check:

   Profile file + @ActiveProfiles activates test config [OK]

Hint: Use profile file plus @ActiveProfiles to activate [OK]

Common Mistakes:

• Setting active profile only in default properties
• Using @Profile instead of @ActiveProfiles on tests
• Relying on environment variable without config changes