Introducing Spring Framework

Chapter 7 ■ Testing Your Spring Application
@Component
@Profile("qa")
public class FileSearchEngineService implements SearchEngine {
}
public List findByType(Type documentType) {
throw new UnsupportedOperationException("QA Environment. Not yet implemented operation.");
}
public List listAll() {
throw new UnsupportedOperationException("QA Environment. Not yet implemented operation.");
}
Now if you change the @ActiveProfiles to qa, as shown in Listing 7-3, and run it again, then you should get the
following output:
2014-02-16 18:22:30,110 DEBUG [main] Using Spring Test fixtures:
2014-02-16 18:22:30,113 ERROR [main] QA Environment. Not yet implemented operation.
The preceding output is the result of running the Profile as QA, and because you annotated the class
FileSearchEngineService with @Profile("qa") the Spring test will use it and you will get that exception.
With profiling, you can get even more detail. You can define a custom Profile by using environment variables; in
other words, you can pass a variable name and if it matches with the value given, then the test method will run. For
creating a custom Profile you need to implement the ProfileValueSource interface as shown in Listing 7-5.
Listing 7-5. CustomProfile.java
package com.apress.isf.spring.test.profile;
import org.springframework.test.annotation.ProfileValueSource;
public class CustomProfile implements ProfileValueSource {
}
public String get(String key) {
if(key.equals("dev"))
return "Development";
else if (key.equals("qa"))
return "QA";
return null;
}
In Listing 7-5, you created a CustomProfile class that will help you to reach every method depending on
a value passed in a special annotation, and as you can see, you have implemented the get method from the
ProfileValueSource interface. Now let’s modify your XML and test class as shown in Listing 7-6 and Listing 7-7.
80