Luc Feys

Forgot to mention, but cannot edit feature request anymore: * Default behavior would be to sort on all columns, in order to guarantee full backwards compatibility with current approach.

Allow PrepAndExpectedTestCase to sort only on filtered columns instead of all columns

Yes, that would be perfect for my use case. I was kind of reluctant to propose this, since at first it felt somehow like patchwork. But giving it some second thought, it could indeed be presented to the user as a proper feature that is easy to understand with proper documentation. I will create a Merge Request.

Hi Jeff, Thanks for your reply. My problem is that the 'expected' datasets are being read from Excel files from a legacy testing framework. And we should still be able to run the legacy tests, so adding a column to the expected dataset could be causing problems (will have to investigate). Also there are a lot of those legacy files, so - even if adding a column would be possible - I want avoid making changes to them, since this will result in a lot of work. I understand that you cannot break existing...

PrepAndExpectedTestCase should only sort on filtered columns

I have implemented all proposed modifications to the two commits, with the following remarks: Added some ITs for VerifyOperation in the first commit Only removed get|setExpectedDataSetAndVerifyTableDefinitionVerifier in the second commit, since the refactor of configureTest is required in order to make the setter obsolete Some additional thoughts/questions: Why are some of the methods in VerifyOperation 'public' (like applyColumnFilters, loadTableDataFromDataSet, ...). They seem pretty generally...

I have implemented all proposed modifications to the two commits, with the following remarks: Added some ITs for VerifyOperation in the first commit Only removed get|setExpectedDataSetAndVerifyTableDefinitionVerifier in the second commit, since the refactor of configureTest is required in order to make the setter obsolete Some additional thoughts/questions: Why are some of the methods in VerifyOperation 'public' (like applyColumnFilters, loadTableDataFromDataSet, ...). They seem pretty generally...

I have implemented all proposed modifications to the two commits, with the following remarks: Added some ITs for VerifyOperation in the first commit Only removed get|setExpectedDataSetAndVerifyTableDefinitionVerifier in the second commit, since the refactor of configureTest is required in order to make the setter obsolete Some additional thoughts/questions: Why are some of the methods in VerifyOperation 'public' (like applyColumnFilters, loadTableDataFromDataSet, ...). They seem pretty generally...