We should have different tiers of tests: tier0 - basic functionality (installation, instance startup, basic operations, import/export, etc.) tier1 - functional tests for the most used features tier2 - functional tests for the less used features and tests that take more time to complete (stress tests) tier3 - long duration tests.
I propose the following separation: Tier0:
basic clu config filter setup_ds
Tier1:
acl attr_encryption automember_plugin betxns cos ds_logs ds_tools dynamic_plugins filter get_effective_rights gssapi import lib389 mapping_tree memberof_plugin monitor paged_results password plugins psearch replication resource_limits sasl schema stat syntax tls vlv
Tier2:
disk_monitoring ds_logs fourwaymmr gssapi_repl memory_leaks tickets
Tier3:
reliabilty
Tests can be marked individually or per module. Py.test automatically collects tests marked with the respective label. For example, to run tier0 tests one can use the following command:
py.test -k tier0
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.1
Commit 9e80a33 fixes this issue
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3412
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.