Thanks Yoann. I just read to code about related to performance test configuration.

The performance tests enablement is controlled by the Maven property org.hibernate.search.enable_performance_tests. By default, the performance tests are not enabled. They can be activated either by choosing the dedicated Maven profile for performance, or by giving the dedicated Maven property:

• Use dedicated Maven profile perf

  mvn clean test -P pref
  

• Use dedicated Maven property

  mvn clean test -Dtest=MyTest -Dorg.hibernate.search.enable_performance_tests=true
  

Then in the JSR-352 performance tests, we need to read the property org.hibernate.search.enable_performance_tests. The quantity of the data to test will changed according to the value of enablement: if performance test is enabled, the quantity will be amplified; else, the quantity remains small, as other normal tests.

So the key point here is, performance tests and normal tests have no difference in term of test-logic / assertions. We don't what to create tests only for performance tests or normal tests. They can work together. When setting the property org.hibernate.search.enable_performance_tests to false, it doesn't mean skipping performance-related tests, it means keeping the quantity to test as small as we can, so test can run faster.