Add ability to merge datasets

Case:

1. Meta dataset is defined and includes several dataset files are common for all tests.
2. Any test is needed its specific dataset in addition to common data in meta dataset.

DataSet in test is override metadataset.

I think it’s a good idea to make some dataset mode flags to manage included datasets, for example:

/*Meta dataset with common data*/
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.TYPE, ElementType.METHOD})
@DataSet(value = {"SomeData1.xml", "SomeData2.xml", "SomeData3.xml"},
        strategy = SeedStrategy.CLEAN_INSERT)
public @interface MetaDataset {
}

@MetaDataset
public class SomeDaoTest {
  ...
  @Test
  @DataSet(value = "before-update.xml", mode=DatasetMergeMode .DATASET)
  @ExpectedDataSet(value = "after-update.xml")
  public void updateTest() {
      ...
  }

  @Test
  @DataSet(value = "before-delete.xml", mode=DatasetMergeMode .DATASET)
  @ExpectedDataSet(value = "after-delete.xml")
  public void deleteTest() {
      ...
  }
}

Possible modes can affect all dataset parameters:

class DatasetMergeMode {
   public static final int DATASET = 1;   
   public static final int BEFORE_STATEMENTS= 2;
   public static final int AFTER_STATEMENTS = 4;
  .....
}

Because default behavior is “override”, only merge is interested.

[artemy-osipov]

Hi, I think merging datasets on annotations, classes and methods is good idea in some cases, but configuring priorities and modes are overcomplication. We can start with choosing good default merging behaviour.

Maybe I’m being too simplistic but my idea is to create (merge) one dataset based on datasets declared on class level (be it metataset or not) and on dataset declared on the test level. So for example if both declare executeStatementsBefore their values will just be merged in one executeStatementsBefore

Agreed! For my opinion datasets on annotation must be specified for common setup like filling reference data, while datasets on methods are more test specific. What do you think about such ordering?

• executeStatementsBefore on annotation level
• executeStatementsBefore on class level
• executeStatementsBefore on method level
• executeScriptsBefore on annotation level
• executeScriptsBefore on class level
• executeScriptsBefore on method level
• datasets on annotation level
• datasets on class level
• datasets on method level
• executeScriptsAfter on method level
• executeScriptsAfter on class level
• executeScriptsAfter on annotation level
• executeStatementsAfter on method level
• executeStatementsAfter on class level
• executeStatementsAfter on annotation level

[rmpestano]

Hi folks, I’ve opened the PR #94, it would be nice if someone could have a look and also try it locally.

Thank you so far!