[
https://issues.apache.org/jira/browse/OFBIZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Gray updated OFBIZ-2259:
------------------------------
Attachment: rollback.patch
Updated version of rollback functionality.
David, the cloned delegator was a bit more work than I first thought and meant
I had to change a few things in various places that could possibly have side
effects so it would be great if you could take another look and let me know
what you think.
Also, there are currently 3 types of thing that aren't rolled back during
testing:
1. Data loaded through the entity-xml test tag, this is because
EntitySaxReader also clones the delegator but I don't why it does that so I've
hesitated to change how it works. I would like to resolve this one before
committing though.
2. Data stored during async service calls
3. Changes to the SequenceValueItem table, I haven't looked but I'm guessing
rolling that back might cause problems and it's not such a big deal anyway.
Regards
Scott
> Testing - Rollback database changes after each test-suite using the
> GenericDelegator
> ------------------------------------------------------------------------------------
>
> Key: OFBIZ-2259
> URL: https://issues.apache.org/jira/browse/OFBIZ-2259
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Reporter: Scott Gray
> Assignee: Scott Gray
> Attachments: rollback.patch, rollback.patch
>
>
> During testing have the delegator keep track of all changes made to the
> database and then roll them back at the end of each test suite. This will
> allow the same demo data to be reused across test suites without having to
> worry about what changes previous tests have made to the data and solves this
> problem regardless of the database being used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
