#725: Move repository test env ops into separate VCS tester classes
--------------------------+-----------------
Reporter: olemis | Owner:
Type: enhancement | Status: new
Priority: major | Version: 0.7.0
Resolution: |
--------------------------+-----------------
There are two approaches in order to be able to write functional tests for
specific repository back-ends
1. Generic test cases that add / remove / ... files in VCS and run them
against
the different repository implementations
2. Test cases for features supported by an specific repository connector
3. Multi-repository test cases
Considering `(1)` above The current code is mono-lythic in the sense that
it's quite dependent upon built-in svn connector. As a consequence a new
test environment class is required in order to activate a different VCS
connector at testing time. The suggested approach consists in creating
classes similar to functional testers allowing to factor VCS code out of
testenv classes and even to load multiple backends in a single test run.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/725>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
