Parameterize integration tests for different constraint types
Reported by Ben Hood | February 3rd, 2011 @ 09:28 AM
ATM the integration tests are date-centric. This means it is very difficult to test
- Constraints for different data types
- Range and Set based constraints
So we need to introduce some parameterization into the integration test suite which will allow us to enumerate through each combination easily.
Comments and changes to this ticket
-
-
Ben Hood February 10th, 2011 @ 01:32 PM
The XML configuration which landed in #178 should make the agent config set up a little more data driven.
-
Paul Jones February 25th, 2011 @ 02:24 PM
This once again proved to be a problem, resulting in #192.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
Ben Hood
Referenced by
-
156
Implement ListQueryConstraints
The data points for the theory based tests have been upda...
-
163
Deprecate AbstractPolicyTest
This ticket is related to #164 and #168, so when
attackin...
-
164
LuceneVersionCorrelationStoreTest Theories
This ticket is related to #163 and #168, so when
attackin...
-
178
Loading and dumping configuration from XML
Potentially we can use this mechanism in the to be revamp...
-
178
Loading and dumping configuration from XML
See #179 and #168 for related follow up work.
-
192
Add ByNameCategoryFunction to category function registry
The fix doesn't include any tests, but then again there i...
-
192
Add ByNameCategoryFunction to category function registry
The fix doesn't include any tests, but then again there i...