sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Implement separate expected-failures files for OC and EOS storage

Browse Source
This commit is contained in:
Phil Davis
2020-08-18 09:31:45 +05:45
parent 55fccdb00e
commit 719c96c5b3
4 changed files with 923 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/testing.md
+3 -2
View File
@@ -97,8 +97,9 @@ To run a single test add `BEHAT_FEATURE=<feature file>` and specify the path to
### use existing tests for BDD
As a lot of scenarios are written for oC10, we can use those tests for Behaviour driven development in ocis.
Every scenario that does not work in OCIS, is listed in `tests/acceptance/expected-failures.txt` with a link to the related issue.
Those scenarios are run in the ordinary acceptance test pipeline in CI. The sccenarios that fail are checked against the
Every scenario that does not work in OCIS with OC storage, is listed in `tests/acceptance/expected-failures-on-OC-storage.txt` with a link to the related issue.
Similarly, scenarios that do not work in OCIS with EOS storage are listed in `tests/acceptance/expected-failures-on-EOS-storage.txt`.
Scenarios from the oC10 API acceptance tests are run in the ordinary acceptance test pipeline in CI. The scenarios that fail are checked against the
expected failures. If there are any differences then the CI pipeline fails.
Additionally, some issues have scenarios that demonstrate the current buggy behaviour in ocis(reva).