Open rsenden opened 1 year ago
For now, potentially long-running functional tests are ignored by default unless the ft.include.long-running
system property is set to true
. We'll need to re-enable the test once we have the possibility to process only a subset of records, for example once #120 gets implemented.
When running the functional SSC tests on an SSC instance that has been running for quite some time, the
ssc.event.list
test may take a long time due to large size of SSC event log (on the current test system, there are about 500,000 event log records, with functional test taking about 45 minutes).Good to see that fcli can handle this large amount of records without errors, however ideally the functional tests shouldn't take this long. Ideally, the number of records to be processed should be reduced, either by adding a server-side query (if supported by SSC), or by utilizing standard fcli functionality for processing only a subset of records (requires #120 to be implemented).