Improve test data

Hi ,

We need to keep existing master data for GW but yeah, all transactions data can be dropped.

We only need master data for unit and functional testing so we can start with moving all sample transaction data out from the core and looks into the option of populate that using a script, maven task, junit test case or something else.

Regards,

Low

Hi ,

“the process Copy Accounts didn't generate UUIDs for the generated records” - that’s a bug that needs to be addressed ?

It's reported in IDEMPIERE-4262, but anyways adding generate_uuid() to the insert will not help here as the migration script cannot record those auto-generated uuids.

Regards,

Carlos Ruiz

Hi,

We need to keep existing master data for GW but yeah, all transactions data can be dropped.

We can keep the current test data (I think is dated 2001 and 2002), and just add new test data, I don't see the need to move the dates to "refresh" the data, having old data is good for example for testing Aging, time-based discounts and other features.

I'm wondering, what about creating a GardenWorld test data set that can be imported via 2Pack.

I think the actual PackInActivator looks for 2packs in the migration folder and applies them on start, so it can be something that can be done on installation time, and we can keep adding new test data in that folder when needed.

Or maybe make it optional, set the 2packs in a different folder, and run the automatic folder packin just on demand on test servers.

Regards,

Carlos Ruiz

Hi and , I know it represents scope creep, but if you would kindly get with () to review the test/populate framework, it would be greatly appreciated. I cannot imagine testing my replenish process without it. It handles time-based entry, multi-step processes, and gives the option to create vertical market testing frameworks.

Thank you for considering! Chuck

Hi ,

Posting of invoice produce the following error/warning for the Euro schema:

Doc_Invoice.getValidCombination_ID: NO account Type=4

Regards,

Low