#50354 Issue #50353 - Categorize tests by tiers
Closed by spichugi. Opened by vashirov.
vashirov/389-ds-base test-tiers  into  master

Download 50354.patch

Bug Description:
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.

Fix Description:
Use pytest marks per test module or individually.

Fixes https://pagure.io/389-ds-base/issue/50353

Reviewed by: ???

I think it makes sense to include some basic tests for replication scenarios (maybe replication/acceptance?). At least a couple of test functions.

rebased onto d5116e93298015a9562bfc7de5f128bf1e386007

Right, I've added replication/acceptance to tier0.

rebased onto 842cea5d8a3d9d4576430f2267078ce90886fb04

Thanks!
LGTM

rebased onto 9e80a33efb1c5b9ef7d4c8a4c362623d61696191

Pull-Request has been merged by vashirov

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3413

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Metadata